There's actually a number of products under the Azure AD name, including:
* Azure AD, their employee/workforce solution. It's a directory, authentication and authorization system. Think Okta or AWS SSO. I imagine this is mostly what the survey was tracking.
* Azure AD B2C, their CIAM solution. Think Auth0, Cognito or FusionAuth (disclosure, I'm a FusionAuth employee).
* Azure AD EI, external identity management (users outside your org).
* Azure AD DS, domain services (older Windows focused services). This subsumes a lot of what Active Directory provided.
And they say AWS has a hard time with naming :).
You can learn more about each of these here: https://azure.microsoft.com/en-us/products/active-directory/ (click on the "AAD" dropdown).
honestly though, Azure's naming strategies do exactly what they say. AWS uses names that are adjacent or completely random (fargate?). i don't even think cognito is a word in english language[0]
Connecting git with an internal AD/LDAP allows for not requiring Azure AD.
https://dev.to/apisix/api-security-with-oidc-by-using-apache...
Azure AD is just Microsoft's version of that directory. The thing is if you use for example Exchange Online, or even just like Microsoft Office licensing, you've now got Azure AD where the users have accounts. Then I see businesses spend a fortune to integrate Okta or similar products that don't actually add anything given how feature full Azure AD is at this point.
Azure Active Directory is the cloud version of Active Diretory. It has some extra features compared to on prem AD (MFA, SSO with 3rd paty apps...) but the whole endpoint management part was moved to another product (Microsoft Endpoint Manager).
The reason so many companies have an AAD tenant is it is set up automatically when you configure Microsoft 365.
[1] https://en.wikipedia.org/wiki/Lightweight_Directory_Access_P...