First published on CloudBlogs on Jan, 05 2016
Howdy folks, Last March I published a blog post with data on how organizations were choosing to connect their on-premises identities (in Windows Server Active Directory) to their cloud identities (in Azure Active Directory). This popular post (over 20k people have viewed it) generated a lot of positive feedback. Recently I've received many requests for a similar blog with updated numbers now that Azure AD Connect has been GA for six months. Azure AD Connect Momentum Let's start with the biggest news we have to share: After only 6 months in market Azure AD Connect is being used to synchronize with more than 24k Azure AD Tenants. We're really excited about the strong growth here! To put this in perspective, every month more organizations start using Azure AD Connect than the total number of organizations who have ever used a third party sync solution with Azure AD and Office 365. Synching users to Azure AD Now, let's move on to some more new/updated data. As of December 30 th , there are now 8.24M tenants in Azure AD and over 550M users (up from 4.9M and 430M nine months ago).
Howdy folks, Last March I published a blog post with data on how organizations were choosing to connect their on-premises identities (in Windows Server Active Directory) to their cloud identities (in Azure Active Directory). This popular post (over 20k people have viewed it) generated a lot of positive feedback. Recently I've received many requests for a similar blog with updated numbers now that Azure AD Connect has been GA for six months. Azure AD Connect Momentum Let's start with the biggest news we have to share: After only 6 months in market Azure AD Connect is being used to synchronize with more than 24k Azure AD Tenants. We're really excited about the strong growth here! To put this in perspective, every month more organizations start using Azure AD Connect than the total number of organizations who have ever used a third party sync solution with Azure AD and Office 365. Synching users to Azure AD Now, let's move on to some more new/updated data. As of December 30 th , there are now 8.24M tenants in Azure AD and over 550M users (up from 4.9M and 430M nine months ago).
- The majority of these tenants are small businesses with <500 user accounts and are not synchronizing from an on-premises Windows Server Active Directory.
- A minority of those 8.24M tenants have >500 user accounts, but because they are comparatively large, they account for 91% of all the identities in Azure AD.
-
Of those larger tenants:
- 75% use a Microsoft sync solution (Azure AD Connect or its predecessors)
- 21% use PowerShell or the Office365/Azure Admin portal.
- 3% use a 3 rd party cloud service
- 1% use a homegrown or custom solution
Fig 1: How organizations with >500 employees Provision users in Azure AD
This data is interesting! First, it shows you that Azure AD Connect is becoming very broadly adopted. It also shows that, compared to 9 months ago, the percent of larger organizations who are using a pre-packaged synchronization solution to provision users into Azure AD has grown from 57% to 78%. Based on feedback from customers and partners we believe this shift is due to the simplicity of Azure AD Connect and the increasing number of large enterprise class customers adopting Azure AD Premium and Office 365. Authenticating with Azure AD Last March when I blogged , Azure Active Directory was averaging just over 1 billion authentications a day. Today we're averaging over 1.3B authentications a day. Of those 1.3B daily authentications:- 45% are cloud only and completed directly by Azure AD (down from 56% in March).
- 37% are federated and completed by an ADFS server at a customer site (up from 32% in March).
- 18% are completed using a password hash that was synced from on-premises to the cloud using AAD Connect or one of its predecessors (up from 7% in March).
- 1% are completed by a syndication partner (large companies who resell Microsoft services)
- Just under 1% are completed by a 3 rd party federation server (i.e. Ping Federate, CA Site Minder, etc.)
- Just under 1% are completed by a 3 rd party identity service (a company like Centrify, Okta, OneLogin, etc.)
- The remaining 1% are completed by a custom or open source identity server
Fig 2: Breakdown of how Azure AD Authentications are completed
Interesting data here as well. The share of authentications completed using Password sync has more than doubled compared to a year ago and ADFS has also picked up 4 points of share as well while the number of cloud only authentications has decreased and the use of third party solutions has held steady at < 4% of the total. Key Conclusions Based on this data, we can draw a few key conclusions:- 75% of tenants with >500 user employees using Azure AD/Office 365 are synchronizing their on-premises Windows Server Active Directory with Azure Active Directory up from 59% nine months ago.
- 25k organizations are now using Azure AD Connect for that purpose and it is far and away the fastest growing solution.
- The use of ADFS with Azure AD/Office 365 continues to grow. It now accounts for 36% of all authentications (up from 32% nine months ago).
- Password sync is the fastest growing method of authentication. It accounts for 17% of all authentications (up from 7% nine months ago).
- The use of third party synchronization and authentication solutions with Azure AD/Office 365 remains flat at ~4% for both sync and authentications.
Published Sep 07, 2018
Version 1.0Alex_Simons
Microsoft
Joined May 01, 2017
Microsoft Entra Blog
Stay informed on how to secure access for employees, customers, and non-human identities, from anywhere, to multicloud and on-premises resources, with comprehensive identity and network access solutions powered by AI.