Azure AD OAuth2 Limits

Brass Contributor

Through office 365 we have Azure AD (basic, I believe).  I understand Azure AD supports an OAuth 2.0 flow that can be used in applications, but what limitations are there on this service?  I understand that the basic tiers have a limit of "10 apps per user" for SSO.  I am a bit confused by this because the language SSO is only used to refer to things like auth through AD FS.  

Is there a limit to how many applications can utilize the OAuth 2.0 feature of Azure AD, per user or even globally?

5 Replies

 For 3rd party SaaS applications you require Azure AD Premium P1 licenses for SSO and Oauth2 

Well that confirms the the worst case.  Thanks for your reply.  It's unfortunate that so much of the platform is held behind Azure AD Premium P1 licenses.  Obviously there is a market where those costs make sense, but for small business P1 would be a 50%-80% increase in total licensing costs, and generally comes with way more than what most want out of it.  Considering how much value a business premium license gets you per dollar, P1 simply is disproportionate when considering cost/value.


Oh well, guess we will have to figure some other avenue for nicely integrating some home-grown apps.

As a quick follow up, if what you say is true, what does this page mean when it says "10 Apps Per User" under the basic and free teir?

Hmm this must have changed, didn't realise this was now possible for free tier...


"With Azure AD Free and Azure AD Basic, end users who have been assigned access to SaaS apps, can see up to 10 apps in their Access panel and get SSO access to them. Admins can configure SSO and assign user access to as many SaaS apps as they want with Free and Basic however, end users will only see 10 apps in their Access panel at a time."


is it a SaaS app or a custom internal app published via the Azure app proxy?

It’s not some 3rd party “SaaS” app.  It actually doesn’t exist yet, and I don’t fully understand Microsoft’s terminology here.  I’m not 100% sure what the role of the app proxy is.  If for example, we develop a web application and make it accessible on the internet (but only to authorized individuals, i.e through azure AD credentials), is this “proxy” component even needed?

The names obviously mean something because the licensing details include them, I just don’t know the difference between “SaaS” applications from a 3rd party, and some home-grown application.  Are all “served” applications that come over the internet considered SaaS now?