When visiting the url - https://developer.microsoft.com/en-us/graph/graph-explorer
In the graph explorer it has a drop down 1.0 or beta. Is beta version 2.0 that Microsoft references in all of it's documentation?
https://learn.microsoft.com/en-us/azure/active-directory/develop/azure-ad-endpoint-comparison
This would be a great question answered because I do not see a drop down for v2.0
There are a couple of things to differentiate here. Azure active directory is the central identity service behind most of Microsoft SaaS services.
It provides two main things
a central identity database that stores users, groups and more. It can be accessed via the graph.windows.net API. Although it's recommended to use the Microsoft graph instead now.
authentication and authorization services. That live mostly under login.microsoftonline.com.
The later provides two versions of the service v1/v2 that implement different capabilities and protocols. (Second documentation link you're providing).
The Microsoft graph on the other hand is the central API for Microsoft 365 services.
The v1 is supported for production workloads, Microsoft is not going to break the API contract and keep the services behind it up and running.
The beta endpoint is where Microsoft makes new things available to get some feedback. Not meant for production workloads. When those new capabilities are ready for prime time, they'll show up under v1.
There's no v2 as of today for the graph. They'll publish a v2 once they need to publish breaking changes to existing capabilities to avoid breaking v1 and disrupting customers.
Related
I am very new to Azure and Azure market place apps.
I could not find any samples in the Web to create an web application in azure market place. I want to create simple web application then i can publish this in Azure market place. For example, this web application simply retrieves all the users in a SQL table and show the list in a html page.
I tried different solutions in web and also here https://msdn.microsoft.com/en-us/library/azure/gg607768.aspx. But could not able to succeed.
I am confused on how to start developing the market place apps. I mean which project template i should use to develop an Market place App.
Can any one please help me how to start developing the web application for Azure market place?
You may check the process outlined in this document Publish and manage an offer in the Azure Marketplace - this article is provided to help - create, deploy, and manage solutions listed in the Azure Marketplace.
Refer to the Marketplace Publisher Guide and Azure managed applications in the Marketplace for details.
Publish a Solution Template: Based on your requirement, you could use the solution templates which allows you to combine multiple items already available in the marketplace to create more powerful solutions.
Whereas, the ‘Publish a Developer Service’ provides fully managed developer services (SAAS) for developers to use in custom application development.
Note: Solutions Template has migrated to the new Cloud Partner Portal (requires registration prior to access).
Additionally, check the Marketplace FAQs (here): Who do I contact with publishing or offer management questions? : Please visit the Azure Marketplace Publisher Guide for up-to-date resource and documentations on frequently asked questions. Additionally, you can log a ticket with Microsoft Support in the Cloud Partner Portal.
We have built a simple mobile app that connects to ASP.net Web-API 2.
We would like to use Microsoft client SDK for it's offline sync support.
Now that Azure Mobile Apps support custom authentication we could actually take the leap.
I want to know out if the offline sync SDK absolutely requires us to use Azure Mobile App or Azure Mobile Services.
Microsoft documentation is full of how-to guides but does not explain what happens under the hood. The best I could understand, both are just OData rest API's and swagger for documentation.
Can the Azure Mobile Client SDK work with API server created on top of ordinary ASP Web-App, outside Azure?
What is it about the Azure Mobile App that makes the magic happen?
Vladmir,
On top of OData, in order to support features like soft delete, offline sync and others, the Azure Mobile Client SDK expects the server to implement a certain protocol. So although the answer to your question:
[does the] sync SDK absolutely requires us to use Azure Mobile App?
... is no, and in theory, you could implement your own API, but I would recommend against doing so, since (among other reasons) even if you manage to implement the expected conventions and behaviors, this will become a maintenance challenge down the road if you need to upgrade the client SDK to take advantage of bug fixes and/or new features.
The good news is that with the latest release of the Azure Mobile Apps server SDK, adding mobile capabilities to an existing ASP.NET Web API application is trivial, and you should be able to enable the scenarios you're looking for simply by adding the appropriate Table controllers. So you can just enhance your existing application and not have to develop and maintain the Azure Mobile Apps specific logic yourself.
About your last question, since both, the client and the server SDK are both open source and developed in the open, you can look at what what makes the magic happen here:
https://github.com/Azure/azure-mobile-apps-net-server
https://github.com/Azure/azure-mobile-apps-net-client
I hope this helps!
The answer for your first question: Yes the SDK can be used in any Server API you have since it will be your entry point to work with Azure Mobile Services.
The Azure Mobile app creates a mobile services instance which has push notifications and SQL tables to store all messages you would like to send with the capability to customize the message as needed. Also it creates a notifications hub instance under the hood to manage notifications for all mobile platforms. Azure mobile apps provide offline capabilities through native sync services between db on your devices and the server when connectivity is present.
Feel free to ask more questions to have a full understanding on How mobile apps works.
Hope this helps.
We're completely upgrading our production and development environment from co-located boxes to an Azure implementation and we'll be developing using Visual Studio Online. Up until this point our dev has occurred on a Remote Desktop environment where developers were logging into Windows server and developing on that RDP box.
We want to set this up and we have some confusion about the Account types/set up types.
It appears there are two ways to set up our Azure and two ways to set up our developers. We are a MS partner w/ some MSDN licenses and Azure credits.
So for Azure we can use our existing MS accounts and just set up an Azure Pay As You Go (PAYG) subscription. This was suggested to us initially but it seems weird to have the entire companies Azure environment going through an individuals live ID. Then we saw we can sign up as an Organization now and it uses Azure AD. We have not been using Active Directory and we're not sure how much complexity this is going to add to our administration. Is there a discernible difference/benefit to going one way or the other?
Then, when we sign up our developers we can either have everyone sign up with their live ID's (we have MSDN w/ VS Premium credits for all developers) or we can set them up using Active Directory with Work Accounts. Having our credits allotted in work accounts sounds like a good way to control things at first reading, but it also seems a bit more complex. I'm wondering if there is much difference between MSDN accounts signed up w/ live IDs or AD Work Accounts. I can't find a real comparison article or pro/con type of discussion anywhere.
It sounds like you have already figured out the main differences. As an organization, I would suggest signing up for Azure as an organization. You can do that here. This is going to give you the management capabilities for resources typically needed by an organization.
Your developers can continue to use the MSDN subscriptions. As Dylan commented, these are not to be used for production environments. You should consider using these for Dev/Test environments and activating your MSDN benefits. This will save you some money. More on that here.
Visual Studio Online will work with your Work Accounts and again give you more control over managing your online resources. This link describes the sign-up process for both Microsoft Accounts and Work Accounts. And if you scroll down a bit you will find your original question specifically addressed.
Finally, you can also add your Work Account(s) to your existing MSDN subscriptions if you like. This way you (and your developers) can use the same account credentials when accessing Azure Subscriptions. Information on how to do that is available in this link.
Your Work Account subscription should be limited to personnel responsible for managing your "production" environment.
After signing up for Azure as an Organization, you can add users to the directory as described here. You can also add "external" users using their existing Microsoft Accounts. It's just a few dialogs to add a user.
I am looking for any option in Windows Azure API Management service, so that I may invoice/cost developers consuming my Web API, as per their number of calls to Web API. Everything I found under this service is quite easy to use and promising, including analytic which shows maximum details of how many times each endpoint is hit etc. The last thing I need is if there is a way I can attach some pricing model with Web API so that I can see total cost invoiced towards a particular developer/consumer for API calls he made.
Azure API Management doesn't have direct support for payments/invoicing. We are working on the management API (coming soon) that could be used for integration with 3rd party billing providers. Would love to hear more about you scenario - please email to apimgmt#microsoft.com
I started to learn everything connected with Azure platform a little time ago. I'm really fascinated how some stuff works like a charm. One of that is AppFabric Access Control Service (ACS) and possibility of Single Sign On (SSO) with Facebook, Google, Live id...
When I was learning how to get running AppFabric I used preview version of it (available for free at https://portal.appfabriclabs.com/, but without SLA). Every tutorial about SSO was based on that Management portal.
Now, when I have my real Azure account (and AppFabric with it) I'm really confused because I can't find anywhere and section on portal where to configure ACS? I want to be able to create relaying party with facebook, live id and google identity provider using real appfabric account? Is that possible?
On some places I saw that this what I'm talking is only preview version of future ACS and that is not in production yet. So, if that is true, my main question is can I use production version (real appfabric account) to do single sign on on my web app? If not, what can I do with current production ACS version? What is the main purpose of it?
If someone have some links where are described main difference between Preview and Production version of AppFabric ACS, I will appreciate that.
P.S - Only tutorial that I found and is considered on current production release of ACS is at https://portal.appfabriclabs.com/. But I don't see integration with facebook, google.. There isn't SSO there...
Thank you in advance.
The current production version of ACS is a subset of what you see in the "Labs". Production currently supports SWT and WRAP. No WS-Federation, no WS-Trust, no (or limited) SAML.
All the cool stuff you mention (SSO for websites, out of the box integration with FB, Google, Yahoo! and LiveID, etc) is available on ACS "Labs" (which is not production yet).