by curiousmindz on 10/1/22, 12:44 PM with 192 comments
by bob1029 on 10/1/22, 2:46 PM
For instance, we are a B2B software vendor in the banking space, and we have to survive all kinds of audits regarding the nature of our code & vendors. By keeping nearly all of our 3rd party items under the Microsoft umbrella, we can automagically skip over vast chunks of our due diligence process (according to the mutual trust equation).
None of our customers is F500 (so far), but we have yet to encounter one who didn't already have AAD, or a willingness to set this up. From a product development perspective, we really prefer having a few known-good ways to do things. Authentication & authorization is one area that I strongly dislike having a large variety of flavors on. Especially considering the nature of our business and ever-increasing demands for complex MFA flows (e.g. SAML). There's been so many fly-by-night operations in this space, and our customers do not have patience for trying new things.
by ascar on 10/1/22, 2:41 PM
83.4% of 500 is exactly 417. The article is also exact about these numbers. No need to add "around".
Edit: Why was the title editorialized to begin with?
Edit2: looks like the title was updated to the original. Thanks.
by sebazzz on 10/1/22, 7:10 PM
That is a big assumption though. A very well known big-four with two letters uses for instance [letters]gs.com ("Global Services") for instance.
by Terretta on 10/1/22, 10:41 PM
85% of big businesses are on the one you don't support.
"Results for the Fortune 500 [to see who's on Azure AD using a] CSV with a list of all the Company Names for all 500 companies. Running it through this script, I find that 417, or 83.4% of companies have AAD, which is just a little off from Microsoft’s public claim of 85%."
https://www.shawntabrizi.com/aad/does-company-x-have-an-azur...
See also this top comment: https://news.ycombinator.com/item?id=33046968
by haxxorfreak on 10/1/22, 3:50 PM
It has similar functionality integrated for discovering if a domain has an associated Azure AD Tenant and enumerating information about users in the tenant, who the "Owner" is and their contact information. As with many Microsoft products there are many configuration options and plenty of them aren't secure by default.
[0] https://o365blog.com/aadinternals/ [1] https://o365blog.com/post/just-looking/
by fweimer on 10/1/22, 4:47 PM
For Google Workspace, a similar URL is: https://www.google.com/a/example.com/ServiceLogin
by PaulWaldman on 10/1/22, 2:46 PM
Could an Okta have a claim against Microsoft similar to Netscape in the late 90's?
by curiousmindz on 10/1/22, 12:46 PM
by vinay_ys on 10/1/22, 1:45 PM
by rootsudo on 10/1/22, 1:52 PM
And much easier to script too. ;)
by wsjeffro on 10/1/22, 3:10 PM
They have a commanding position in the enterprise. What’s keeping them from crossing those enterprise boundaries?
by tluyben2 on 10/1/22, 1:40 PM
by mberning on 10/1/22, 2:37 PM
by unreal37 on 10/1/22, 1:49 PM
Some companies use a different domain for corporate use than their public domain name.
Like fb.com
by OrvalWintermute on 10/1/22, 1:57 PM
by pid-1 on 10/1/22, 1:37 PM
by chayesfss on 10/1/22, 1:39 PM
by idiocrat on 10/1/22, 1:47 PM
by petercooper on 10/1/22, 7:14 PM
by ocdtrekkie on 10/1/22, 7:22 PM
by kn8 on 10/1/22, 2:20 PM
by dan000892 on 10/1/22, 4:23 PM
Interesting (to me) is that the OpenID configuration endpoint provides the tenant ID for not only Commercial tenants but US Government (GCC & GCC-High) as well because the Azure AD portal has relatively new functionality to configure cross-tenant access settings by tenant ID or domain name but Gov tenants require you to obtain the tenant ID from the organization which is either security through obscurity or due to use of some Commercial-only Graph API call.
by ZiiS on 10/1/22, 2:52 PM
by altdataseller on 10/1/22, 7:48 PM
by simonw on 10/1/22, 8:15 PM
by cloudking on 10/1/22, 5:14 PM
by computerfriend on 10/1/22, 3:00 PM
by vondur on 10/1/22, 5:16 PM
by parkingrift on 10/1/22, 2:54 PM
by sabujp on 10/1/22, 2:28 PM
by not_enoch_wise on 10/1/22, 2:20 PM