What is your primary use case for Azure Active Directory?

My main use cases for Microsoft Entra ID began with it serving as the authentication back-end for Office 365 investments; now it's starting to function as a federated IDP for us.

The main use case for Microsoft Entra ID is the replication of Active Directory, where we manage all of our users. This is the most popular thing that we do, and we use PIM and Conditional Access as well.

Our main use cases for Microsoft Entra ID involve working with clients that use the Microsoft platform and their identity graph to identify who the users are and integrating our solution with Microsoft Entra ID to identify who that person is when we're registering credentials on a YubiKey. Since implementing Microsoft Entra ID, we have not seen major changes, but we are working with Microsoft to examine metrics and build dashboards in Sentinel. We have plans to do that, and we have a pull from the customer perspective wanting to examine the data metrics. Our data metrics are specifically tied to the lifecycle management, onboarding, usage of authentication, enrollment, and recovery cycles. We just met with the team to work on this and determine how we can use agentic AI to share risk signals both from our metrics and for the Sentinel dashboard.

My organization's approach to defending against token theft and nation-state attacks since implementing Microsoft Entra ID does erase a few of the common attack vectors that are worth solving. Prior to adopting Microsoft Entra ID, I was using another solution to address similar needs.

Microsoft Entra ID acts as the central identity plane for most of our applications, and our customers rely heavily on that. It is the central backbone of everything that gets into their company. The network was the perimeter before, now it is identity, and from an identity standpoint, Microsoft Entra ID stands right up there. It is the gatekeeper for all company resources; anything has to go through Microsoft Entra ID for authentication, authorizations, and all the validation access controls before they get access to any resource.

My main use cases for Microsoft Entra ID include general identity management, identity protection, identity governance, identity security features, access reviews, logging and auditing, and overall protection. Now that it has been transformed into more of a Zero Trust control plane, I am utilizing the Zero Trust components as well.

My main use cases for Microsoft Entra ID are authentication and single sign-on for multiple applications, both Microsoft and other systems.

My main use cases for Microsoft Entra ID are all access to anything and everything Microsoft.

Seamless single sign-on into various destinations within the enterprise application space is a main use case for Microsoft Entra ID. ADP uses a variety of different applications throughout the organization, which serves as a common thread connecting those various applications.

My main use cases for Microsoft Entra ID include Azure App Registrations and management of third-party integrations into our M365 tenant.The implementation of Microsoft Entra ID has been pivotal for our secure access to apps or resources in our environment. We use Microsoft Entra ID to grant access for all external apps that want to connect into some type of data source in Office 365, so it has been crucial to be able to set those up and manage those.Microsoft Entra ID's integration capabilities have been the foundation for our Zero Trust model because my team only sets up integration and Azure App Registrations based on a request and we review them. Nothing gets access to any data or anything in our tenant unless we review it and approve it and configure it in Microsoft Entra ID.

My main use cases for Microsoft Entra ID are authentication and access management.

Microsoft Entra ID serves as the main use case for everything, supporting M365 and all related services, with Entra ID being a key component for everything.

My main use cases for Microsoft Entra ID are managing all users and everything related to user management.

We use a hybrid environment with Active Directory and Microsoft Entra ID along with SCCM. Our hybrid setup with Entra and Azure allows us to use role-based groups for access while keeping our AD environment intact. We sign our automation based on Active Directory and use write-back for populating new groups. We are able to use the enhanced security from Microsoft Entra ID while maintaining our existing environment. Our company has been slow to modernize in the cloud environment and we are on the tail end of the actual conversion. We conduct a lot of pen testing with our existing accounts because we still use Active Directory. We haven't had a lot of incidents with identity management. We are just getting into issuing out cloud PCs, having done that in the last year. Some of the more advanced features on Microsoft Entra ID have not been implemented yet.

I have been using Microsoft Entra ID since its release. My main use cases with Microsoft Entra ID include identity management, lifecycle management, account creation, and access management within Entra. Currently, we are exploring Microsoft Entra ID governance and looking to expand in that direction. Overall, everything around account management and identities management within Microsoft Entra ID itself, from creation to deletion, represents our primary focus.

My main use case for Microsoft Entra ID is for access control. I'm not entirely sure what I like the most about Microsoft Entra ID, but perhaps it's that everything is included in the same app compared to before. Mainly, we have SharePoint set up, so we use it to manage users' access, which is the main purpose.

Digital Workplace Cloud Infrastructure Administators

Our main use cases for Microsoft Entra ID include single sign-on into every application, even third-party.

My main use cases for Microsoft Entra ID are primarily for Active Directory and tenant management, as well as software authentication.

Our main use cases with Microsoft Entra ID involve extending our on-premises Azure into the cloud, starting with messaging in M365 and syncing the IDs up, but we also do a significant amount of work with enterprise apps, app registrations, and different types of identity within Azure.

Microsoft Entra ID is used for hybrid synced users to Azure and for external users with guest accounts created in the directory. Security groups and all related functionality are utilized for user management. Logging activities, including sign-in logs, password lockout, and security monitoring for compromised accounts, are valuable components of the implementation. To prevent intrusions, as a government entity, Microsoft Entra ID is used to determine if someone is attempting to brute force an account and to understand the origin of the access attempt and whether it represents an actual threat.

Microsoft Entra ID is used for identity as the main use case.

Microsoft Entra ID is mostly integrated with Microsoft 365, and it serves as the backbone of the 365 services. Microsoft Entra ID identity platform is feature-rich, allowing for a lot of integration as a single identity model. As an identity provider, you can get a lot of external SaaS applications to identify and be authenticated via Microsoft Entra ID, which is very useful, allowing you to secure your identity in one central place as opposed to trying to secure it in multiple different environments or needing to authenticate users individually on different platforms. Authentication happens once through one identity platform. The Conditional Access policies that you can drive and control the identity flow through are also very useful.

Microsoft Entra ID houses all of our users, and we conduct all of our identity and SSO and protection through it. Our sign-in logs go through Microsoft Entra ID, so we have everything, and it's how we build all of our access policies and how we determine who can access what from where and what we trust and what we don't trust.

My main use cases for Microsoft Entra ID are protecting company data and authentication. We use on-premises Active Directory and sync everything to Microsoft Entra ID, and we protect all of our apps with single sign-on and multi-factor authentication.

My main use cases involve daily usage as a system technician, running InTune and Microsoft Entra ID, mainly for endpoint and user management. The main metric demonstrating the impact of the integrations is that we use Microsoft Entra ID for all of our devices. When assigning or removing users, if a user is terminated, or a device is lost or stolen, we use it to remove and manage all endpoints. User migration occurs when we have new hires or terminations, and most of that is what I actively use it for.

My main use case for Microsoft Entra ID is full identity management and system security.

My main use cases for Microsoft Entra ID are identity and using Conditional Access to lock down security measures and ensure people are not engaging in risky activities when signing in from home.

We are hybrid, so we mainly use Microsoft Entra ID for control of users that we've synced out to the cloud.

Our use case focuses on ensuring company security through authentication, two-factor verification, groups, and access management. This includes SSO, SFTP, FTP, to manage access for both internal workers and external users who need to access our system.

I'm developing a SaaS application. I'm working with a company that develops a SaaS application where the first customers are Azure customers. Most of our customers are using Microsoft Entra ID as their single sign-on implementation. I saw not only my organization's Microsoft Entra ID configuration but also others.

My primary use case for Microsoft Entra ID is service principal management for API access and infrastructure access to Azure and similar systems. We also use it for single sign-on into some applications, such as SAML and OIDC applications.

Our primary use case for the solution is building solutions using all Microsoft services, including migration projects, service provider roles, developer solutions, AI solutions, and ETL solutions for all those things, where we will use Microsoft services.

I work on it to investigate it. I work at a cybersecurity company, so I focus on how the product behaves, particularly how Microsoft Entra ID behaves with group permissions and such. We work with Microsoft because we're also a security company, so we scan Microsoft Entra ID and then monitor what happens regarding defending against token theft and nation-state attacks. We are partners with Microsoft. We don't sell Microsoft products; we sell our own product, but we integrate it with Microsoft.

My use cases for Microsoft Entra ID mainly include single sign-on, PIM, and conditional access policies.

I handle access management.

My main use cases for Microsoft Entra ID are that the whole back office platform is based on it. We're using Teams or other tools for our day-to-day usage of Microsoft Entra ID.

We predominantly use Microsoft Entra ID for running our User Directory Service. It integrates with Intune, Exchange, and SharePoint.

I have been dealing with Microsoft Entra ID, which is not as an Azure product, since 2000. So, twenty-five years now. It is now known as Microsoft Entra ID.

Our primary use case for Microsoft Entra ID ( /products/microsoft-entra-id-reviews ) is mainly for single sign-on (SSO ( /categories/single-sign-on-sso )). We use it to log into other cloud-based applications. We have an internal sync from Active Directory to Microsoft Entra ID ( /products/microsoft-entra-id-reviews ). Whenever an account is created in Active Directory, we immediately create an account in Microsoft Entra ID to automatically grant access to cloud-based applications. Some roles are assigned based on Microsoft Entra ID data.

We use Microsoft Entra ID ( /products/microsoft-entra-id-reviews ) for authentication purposes and are planning to implement additional modules like Mobile Device Management ( /categories/mobile-device-management-mdm ). Our current use is mainly for integrating third-party applications for distributed applications to centralize authentication.

I usually use Microsoft Entra ID to access our resources and to manage our approvals. It is used to assign roles, set limits, and manage access levels. For specific users, I ensure that nobody else has access. My personal files are protected, and confidential projects are kept secure.

I am currently using Microsoft Entra ID ( /products/microsoft-entra-id-reviews ) and have been working as a user and administrator for nearly two years. It serves as an ID management tool which used to be called Active Directory on on-prem servers. With the transition to the cloud, it became Microsoft Entra ID ( /products/microsoft-entra-id-reviews ).

We are using Microsoft Entra ID for single sign-on with our hybrid domain environment and for identity management with multi-factor authentication using Microsoft Authenticator. We plan to migrate our whole user base over to Microsoft Authenticator with MFA capabilities, possibly with certificate-based authentication.

We implement standardized conditional access policies for our customers using Microsoft Entra ID, mainly for security, governance, and conditional access. We also sync on-premises Active Directory accounts to Microsoft Entra ID to manage groups and Azure resources like Azure Virtual Desktop.

We primarily use Microsoft Entra ID in hybrid scenarios where we are undergoing digital transformation. We had on-premises Active Directory that we transitioned to Entra on the cloud, enabling users to authenticate with their regular credentials.

I have demo tenants where I test lots of features, such as creating test accounts and managing permissions.

We have been using Microsoft Enterprise for ten years, and we actually started beginning to really use it about two years ago. Earlier, we had an access manager on the premises, but everything is moving to the cloud. So we are moving our access management and identity management solutions to the cloud as well.

The primary use case is for single sign-on, service provisioning, and security features, including multi-factor authentication.

I use Microsoft Entra ID daily as an end customer in an enterprise environment. We are using it for very simple use cases such as authenticating with SSO to third-party solutions.

We primarily use the solution for our AD. Azure AD and Microsoft Entra ID are basically the same, they are currently rebranding. I basically manage users and permissions.

Our primary use case for this solution is identity and access management within our organization's hybrid cloud environment. We have a multinational presence across 12 countries, with around three thousand employees worldwide. Entra ID plays a pivotal role in streamlining user onboarding and offboarding processes, ensuring secure access to our resources. Our environment is characterized by a blend of on-premises and cloud-based services, and Entra ID seamlessly integrates with our Azure tenant. It allows us to efficiently manage user identities, enforce authentication and authorization policies, and implement multifactor authentication for enhanced security. Moreover, we leverage Entra ID's capabilities to maintain compliance with specific regulations, such as those in Germany, where mailbox access for departed employees requires careful management. Entra ID's security features, including Azure Information Protection integration, provide an additional layer of protection against evolving cyber threats.

We are using Azure Active Directory to secure our identity and applications throughout our corporate. All the authentication is done automatically.

The use cases typically include external customer authentication, which we do, and by customers, I mean our hotel partners. There is basic user authentication and the ability to isolate those users based on a particular security environment, whether they are coming from a PCI environment, lab environment, corp environment, etcetera. Each of those has to pass through specific security, so everything that your Active Directory or Windows AD is solving on-premise is essentially the use case, except for the external customer situation which was the one thing that made me look at Entra ID. Unfortunately, the way Entra ID works created a major security issue that I cannot go into regarding guest users for our tenant. We are now trying to fix that.

We use Microsoft Entra ID primarily to reconnect all of our Windows laptops. It is our centralized location for access to pretty much anything web-related. Everything you log in is MFA activated. We've worked on conditional access policies in it as well.

I use Microsoft Entra ID in my company for provisioning and deprovisioning identities and access.

We use Entra for things like, multifactor authentication, user backups, registrations, and other identity management tasks.

We use the solution for single sign-on.

My organization uses Microsoft Entra ID for some people who access Azure, especially for people who need Azure for different things. My organization deals with people transitioning from a standard data center environment into a cloud-based one to meet their needs. My organization has certain conditional access to certain people because we have access to government and cloud services or a commercial environment, along with different versions of each of those across different groups. I would say that most of our organization's work is just giving conditional access to people and occasionally vendors, but nothing too absurd.

We use it for access and identity management.

We have it synced to our on-premises Active Directory environment where we have some Active Directory servers. We use it for authentication into our cloud apps. We use it for SSO. Because it is connected to our Office 365 tenant, we use it for single sign-on for applications that support it. We also use it to evaluate risky sign-ins or risky activity for users. If there are user sign-ins from a geographic location that they would not normally sign in from, we get a notification for it, and we can investigate what is going on with a user's ID, if the person is actually there or not, and if we need to take any action on it.

We manage local users in the Microsoft Entra ID environment.

We migrated about 3,000 computers from on-prem Active Directory to Azure Active Directory or Azure AD.

It is the primary ID platform that we use. It is where all our users are homed. We have Intune integrated with it as well. We use it for authentication. We still have some on-prem infrastructure, which uses legacy or traditional on-premises Active Directory, but all the endpoints and all the users are homed in there. We integrate with single sign-on for a lot of applications, such as Monday.com and ConnectWise. There are a lot of other tools there, and we use Entra ID for them as well. We use the multifactor authentication functionality in there and then Intune as well, which technically is not a part of Entra ID, but they are very close-knit. We use that for software deployment onto devices, and then we have been on Autopilot for device building and everything like that. It is the center of a lot of what we do.

I use the product for user policy and group management.

Microsoft Entra ID is used for user management and directory governance, including conditional access management, sync user management, group management, and application and SSO connections. In short, it is a user, policy, and access management solution for environments with 10,000 to 50,000+ users.

We're using the solution for our customers. It's for those that may have been on-premises and moved to the cloud when it started to become mainstream. Users wanted to transfer their users and permissions and so on to the cloud and onto Azure.

There are many use cases. The main use case is identity synchronization to on-prem with AD Connect. Another main use case is related to conditional access. Automated licensing is also one of the use cases. It is also used for identity access management with specific workflows, rules, etc. Permission or role management for applications is another use case, but I have never used that in production. I have demonstrated it to multiple customers, but they were not there yet.

We use it as the Active Directory on the cloud. We have the systems on-premises and on the cloud. We connect the AD data to Azure. We have a single sign-on service on multi-cloud. We use the single sign-on feature on, for example, AWS. In terms of the version, we use it as a service, and it is always updated to the latest version.

We used Azure AD for a role-based customer access mechanism. We implemented a single tenant, single sign-on for users of the application. We gave them a sign-on feature with OpenID Connect.

We primarily use the solution for user integration; we have many users around the globe and use it for authentication syncing in Microsoft 365 and SSO, and the product provides a single point of use. Our environment encompasses many offices around the world.

I am using Azure AD to assist a client with COCC level one and level two certifications. The primary use of the solution is its conditional access feature to enforce fine-tuned and adaptive access controls. The robustness of a zero-trust strategy to verify users has helped in implementing zero trust right now.

The main use case for Entra ID is to move from on-premises to the cloud. I have been doing a lot of cloud transformation work, and I have seen that most organizations that move to the cloud see a lot of benefits in terms of monitoring and IAM. In those cases, we move to Entra ID.

We use Azure AD to manage all endpoints, including laptops, desktops, mobile devices, such as iPads and iPhones, and users. We can disable accounts, create accounts, reset passwords, maintain access, and manage permissions.

We use Azure AD to implement conditional access when using Microsoft Network (MSN) services. Our infrastructure is primarily on-prem, and we operate our email in a hybrid environment and use the solution for continuity between our on-prem and cloud landscapes.

We use the solution to cover Microsoft 365 licenses.

We use Office 365 for our emails and Office. As part of that, we have Active Directory on the cloud. We want to safeguard things, keeping in mind the recent upsurge in cyber attacks.

It gives us security when integrating all the Active Directories of all our branches together, giving us a centralized database and authentication.

Azure AD is primarily used as the backend for all Microsoft Office 365 user accounts and licensing, as well as for securing those accounts. Endpoint Manager is also utilized, which is part of domain control in the cloud, even though it is not Azure AD.

I set up Azure Active Directory for many customers of the company I work for. I'm an implementer. It is the basis of identity and access for all the tenants we are using for our customers.

We use it for identity and access management for cloud-based applications.

We are a university using Azure AD to authenticate staff, faculty, and students. Our organization completely depends on Azure Active Directory for authentication and identity-related features. All cloud activities and third-party services are validated with Azure Active Directory. We also have an on-premises Active Directory, and the data is synced periodically to the cloud. Most of the services done on-premises are reflected in the cloud at once. We can also do the same handling features from the cloud to write back to the on-premises AD. This is the architecture.

We had the need to integrate the solution that we had on-premise and the email-based identities, so we looked for a solution from the same provider that could establish us and provide a synchronized identity (what we know today as SSO) in our resources and thus be able to log in with the same identities we had on-premise and in the cloud. We wanted to take advantage of that synchronized identity quickly, simply, and safely. It was important to understand that users today want to have a single password for all resources, be they applications, or devices, in order to help them so that they are not constantly learning different credentials and can thus be faster and more efficient when establishing a single login.

We are a Microsoft-oriented company. All our main infrastructure for user systems and productivity, like Microsoft Office and email, are from Microsoft. So we use Microsoft products and we use Active Directory on-premises. We have also built a cloud infrastructure and we now have a completely hybrid architecture. As a result, it was mandatory to configure Azure Active Directory to synchronize with the on-premises Active Directory. We have finished that project and now we use Azure Active Directory for users who are on the cloud.

We use it for various things in the organization: * Provisioning access to systems in the cloud for either internal teams or our partners' external teams. * We use Azure AD for Windows device management with Azure AD Intune. We use them for the management of devices. We have company devices, laptops, or tablets all using Azure AD. * Within Microsoft Azure, we use various services, e.g., Office 365, for granting the right level of access to the right people. I am directly involved in the project. I know what is happening and being done by developers. I have also done some hands-on work in a test environment, using my own account, just to learn.

Azure AD manages the identities of all our employees.

We use it because we have to onboard our user laptops to our Windows domain. Azure AD provides us with the Windows domain capability.

We are using the solution primarily for demo purposes. We use active data cases from Microsoft. You can run different kinds of virtual machines and different kinds of services. We're currently using it in production.

Anyone who moves to Azure must have Azure Active Directory. Azure Active Directory is identity management.

We use it for authentication. Where we have cloud services, it syncs with Active Directory on-prem. We have about 1,800 people using it.

We are using Azure Active Directory in our company at a group level.

We are using it for authentication. We are using GPOs for user and computer policies.

We use this solution to authenticate to the portal. There are also some VMs that are not domain-joined, so we use Azure users that we create natively in the portal. We also use it for our applications. The accounts that we create natively in Azure are used for application authentication. We have a hybrid deployment model where some accounts are primarily native in Azure, whereas others are on-premises. We also have accounts that are synchronized between our on-premises servers and Azure.

The solution is our main authentication on our authorization platform to get access to our resources. The solution is deployed on cloud with Microsoft Azure as the provider. We have around 100 people using this solution in my organization.

My main use is for directory services, including identity access, management policies, access control, authentication features, and endpoint management.

I have been working with a medication company and we are building an LMS system. We have an older version and we've decided to develop a new version of it. We are building the entire system on the cloud and using new technology. We started the process on Azure cloud, but we have later plans to try AWS, but for now, we are using Azure Active Directory.

The solution is being used at Kuwait University for different things, such as email systems.

We use Office 365. We have different licenses because our users are using mail, mail strategies, Microsoft Teams, and the Office package. We use a lot of different services. We use Microsoft Intune, which is connected to Azure and other services like Conditional Access, which we also use. Microsoft Defender is another one, which is also connected to Azure. The solution is deployed fully in the cloud through Microsoft Azure. We are using the latest version. The solution is on cloud, so we cannot control the version we're using. That is controlled by Microsoft.

The solution is deployed on a public cloud. We are using Microsoft Azure.

Active Directory is used for authentication and provisioning for users and devices and granting them access. We're in a hybrid mode where we still have on-prem controllers as well.

I am a systems manager. I use Azure Active Directory every day for my support job. Our authentication tools to single sign-on portals are hosted in different cloud products, like Amazon or GCP. So, we create an enterprise application and Azure Active Directory to give our users for authentication access to various public URLs.

We use Azure Active Directory for quite a few things. We use it for security group management of authorized principals who need access to get SSH-signed certificates for user logins. We use it for automated jot-based (JSON Web Token) self sign-on for our lowest, least privileged credentials on certain products. We also use AAD for B2B coordination of SSO when we're bringing users onto our platform, where they have Active Directory on their side. We use the OIDC-based SSO flows through AAD to merge project-level AADs back to our corporate AAD for internal single sign-on flows.

We use Active Directory to manage our main database and control students and staff access with rules and passwords. Usernames, emails, etc., are all integrated with Active Directory. Office 365 is also integrated with our Active Directory.

We primarily use the solution to take users into our AD. That's the basic purpose. We are using it in our whole organization so that our AD is synced.

We are using it for all non-structured data and as an identity manager for all of our accounts. In addition, we use it also to authenticate Google services, because we have Google Workspace for email, and to integrate other tools with our services. We are able to keep it all going, balanced, and synchronized. It's very good. We use it for just about everything that we need to do an identity check on.

The solution is our main identity provider and federation platform. We use it for authentication and for federations, for some provisioning, and a little bit of governance.

We have integrated our internal applications and cloud applications with Azure AD. We also have a few external applications for which we need to implement a self-service portal and handle requests such as password reset. We have external applications such as Cloudspace, and we have integrated Azure AD with Cloudspace. We mainly use a single sign-on. Our main target is to go through all single sign-on applications and integrate them with Azure AD. We also need to audit everything in Office 365. Our mail system is Office 365, and we also do some auditing. We are also implementing Intune. We have deployed some basic policies for mobile devices, and we are working on improving those policies. We need to configure conditional access and improve policies for the applications and devices. We are doing some testing, and it is in progress. In terms of deployment, we have a hybrid deployment of Azure AD. We have the 2019 version of AD on-prem.

We provide single sign-on, app syncing, and API seamless access to more than 2,000 users with the syncs into Azure. We provide access to email, SharePoint Online, Skype, and other services on the cloud to half of those users. We have services in the cloud, such as app registration and documents for SharePoint Online.

I have been using Azure Active Directory mainly for access management, identity governance, access reviews, and patent management.

We're using Azure AD as a centralized identity management tool, to keep all identities in one place. For example, if we have an application that needs authentication, we use Azure AD. It is not only for user authentication and authorization. We also use Azure AD as a synchronization tool from on-premises instances to the cloud, and we are using Azure ID Join to join machines directly to the cloud. We use it for access policies, as well as the registration of services.

I use a Microsoft 365 cloud deployment and I have an organization where users are created. All of these users are hosted in Azure AD. I send emails in Exchange Online. For collaboration, we use Teams and SharePoint. Basically, all of these Microsoft products are on Azure AD. This is due to the fact that for you to use any of these products, users have to be created and these users are being hosted in Azure Active Directory. Without the users in the first place, the products are not used.

We use the Azure portal to create users, assign rights, build policies, etc. I'm not an administrator for that part of our system but that is basically what we use Azure AD for.

Containerization is mainly what I've been dealing with lately. I've been trying to provide solutions with Active Directory and cloud resolutions so that Edge services can communicate properly to the main data centers. We use Active Directory for global authentication.

We use Azure AD for sign-on security as well as for our customers' Microsoft 365 solutions. We help migrate our customers from the traditional Active Directory, and to use Exchange Online and Microsoft Teams. We use Azure AD to secure their login processes with multi-factor authentication. In some specific cases, where there are specific applications, databases, or Active Directory login information about users, we integrate Azure AD with those elements.

Azure AD is primarily integrated with all of the Microsoft services, such as Microsoft 365, Office 365, and Dynamics 365/Power Apps. Behind the scenes, we are, in one way or another, using Azure AD for our application security, identity management, and to access purpose services. At times, we need to configure some advanced features to provide access and identity to third-party apps to integrate with Dynamic 365.

When a customer is trying to synchronize user information from their on-premises environment to the cloud, they might be encountering a series of errors or they may not be able to achieve what they are trying to achieve. They will raise a ticket so that somebody can help resolve the problem or clarify the situation and explain what the workflow should be like. That's where I often come in. My support scope is focused on the synchronization aspect of Azure Active Directory. My specialty covers scenarios where customers have information in their on-premises environment and they want to synchronize their Active Directory information into the cloud with Azure Active Directory. In addition to getting on calls and assisting customers to resolve issues, we also try to help educate customers on how to achieve the best results with Microsoft products.

We have users, groups, and applications, and the purpose of this product is authentication, authorization, and attestation. We use it for the services connected to those three "A"s. The use cases in all organizations are more or less the same, even if some side services differ. Azure AD is used for authentication and authorization. It's about managing identities and granting access to applications.

My primary use case with Azure Active Directory is configuring applications, for example Edge, on premises and doing synchronizations with ADFS in a hybrid environment. I have used it in a lot of application integrations. I set authentication for the hybrid and cloud applications for the services that we acquire.

We are a small consultant company, and we help customers to build hybrid environments. We synchronize on-premises AD to Azure AD and help our customers decide which one they want to use. In our own company, we use Office 365, so we use Activity Directory directly for authentication and authorization.

My company provides different types of support for different products. I am a Microsoft Azure support engineer for Azure Active Directory. We work with multifactor authentication, federation, synchronization of on-premise services to the cloud, migrations from on-premises to the cloud, and role-based access to company services. I also work with the identity services of Azure. I work with certain cases where customers have issues with Office 365. That's because the administration and the role-based access come from the Azure platform. We're in the middle of the transition to unify more services. There are many services in terms of networking with the machines and storage accounts. Azure is a platform, so it doesn't have a version.

We are using it for central management, MDM, SSO, MFA, applying policies.

My primary use case is for Azure Active Directory is user management, creating users, assigning them access to network resources, network drives, resetting passwords, and dissembling users.

We use Azure AD for user access and control. Our deployment is a hybrid of on-premises and cloud.

Our use case for Azure AD is principally to do the role-based access management for our resources. So, we essentially use it for authentication operations for our primary groups and users to secure access to resources.

I use this solution as an identity platform for Microsoft Applications including Office 365. We have found that users have third-party applications for authentication using an integrated identity infrastructure.

I was a consultant. I recently changed my job (seven days ago). Most of my customers did everything in Azure. They used Azure Active Directory Domain Services (AD DS) as well as Active Directory Federation Services (ADFS) to sync a user's profile using AD Connect and a federated model. So, they could access an application on-premises as well as in a cloud. I am now a CTO for a big hospital. I manage Azure AD for all hospitals as the CTO. They also use Office 365 across all four of their hospitals. The solution is hybrid cloud. We have the Active Directory on-premises and Active Directory Domain services in Azure. This is where I use AD Connect (or sync server) to sync the user's profile.

Azure Active Directory is similar to an on-premises access control system, but the service and data are hosted in the Azure cloud. Previously, everyone used to have Windows servers built as domain controllers for Active Directory to store their employee data. This assumed the role of a database for their employees. With Azure Active Directory, which is in the cloud, you have the same functionality and there isn't much of a difference. The defining point is that you have access to online, cloud-based resources, such as Office 365. In my company, as well as others, we had already implemented the on-premises Active Directory for our infrastructure. We leverage Azure Active Directory to synchronize the existing on-premises details to the cloud so that it creates an identity in Azure, which allows it to be used for other SaaS-based solutions.

We use it for all of our internal colleagues. Every single user is synced from our internal on-prem directory to Azure AD. Every single user has a presence in Azure AD and that account or identity is then used for at least 10 to 15 different applications. They directly query what groups they're a member of within Azure AD. We use Azure AD for at least 15 different applications.

Azure AD is where our primary user data is stored. We get a feed-in from our HCM solution and it creates our users, and then that's where we store all of their authorizations, group memberships, and other relevant details. We access it through the Azure Portal.

We are a system implementer and this is one of the products that we provide to our clients. We primarily use this product for identity and access management. Any of our customers using Office 365, which includes Exchange Online and SharePoint Online, are using it for authentication. Worldwide, there are a lot of use cases. The identity check includes whether the username and password are correct, and it also supports multifactor authentication.

I am a cloud engineer, and I do a lot of administrative work that involves creating new infrastructure for our applications. Whenever I create infrastructure, I have to install it on our Active Directory and then set it up. This is how it was that I started working with Azure Active Directory. Once the infrastructure is set up, I usually proceed to create user groups and user IDs inside Active Directory. After they are created, I set up and configure them based on the requirements of the organization, including the access required for different groups and users.

We primarily use the solution for business intelligence and analytics.

We run in a hybrid model. We have our Active Directory on-premise directory services that we provide. We basically went to Azure so we could provide additional capabilities, like single sign-on and multi-factor authentication. We are running in a hybrid environment. It is not completely cloud-native. We sync our on-premise directory to the cloud.

I use it for managing identities, access, and security in a centralized way. I help other people use this product.

The use case for this solution is the access to Office 365, Azure subscriptions, and several software as a service platforms as well as other SaaS-developed applications that we provide access to, such as, OpenID Connect, OAuth, or SAML.

BDO is a network of firms and a firm is what we call a country. So, we are present in about 160 countries. I am involved in BDO Global, which is not really a firm in the sense that we don't deal directly with clients, but BDO Global hosts IT services for all those 160 countries. A couple of those solutions are a worldwide audit solution that our firms use for financial audits for customers. We have a globally running portal solution, which firms are using to collaborate with our customers directly. All these services are basically based on Azure AD for authentication and authorization. This has been a lifesaver for us, because BDO firms are legally independent, so, we don't have a single identity store worldwide, like other big companies potentially do. We created an IAM solution based on Azure AD that ties all 160 dispersed identity stores back into one. We use that to give access to our services that we run globally. Azure AD doesn't really give you a version. You just need to take the version as-is because it is a service that Microsoft delivers as a SaaS service. So, we don't have a lot of influence over the version that we use.

We have an Azure active directory and we also have our own on-prem AD instances. We basically use the solution for user management, group management, policy management.

We use it mainly for our Office 365 files. The integration between the two is interesting. It's been a learning curve.

The solution is a hybrid cloud with connectors into Azure/Microsoft 365 cloud.

A lot of our clients basically want to go to the cloud and they don't know how to proceed with doing so. The first thing we recommended is to make sure their identity is in Azure AD as a hybrid approach. We're not getting rid of their on-premises environment, and instead basically, if they're planning to go to Office 365, they will be able to take advantage of the Azure Active Directory.

We use it to have better security and better control over PCs and clients.

We use it for the authentication of people in a hybrid configuration. In most cases, Office 365 makes companies move to Azure Active Directory. We have both on-premises and cloud deployments.

Typically, we have applications deployed within the office network that we need to make accessible to our staff outside of the bank. Some of them are also our clients, but mainly, this is for people working in the region. So without having to put them behind firewalls, what we opted to do is publish them to the proxy. This means that they can then come in via a secure port and begin to access the resources as if they were internally and securely within the network.

We primarily use the solution only for the employees. It offers a single sign-on to business applications. Internal modern applications also go through Azure Active Directory, however, we use Active Directory for the legacy ones. (Kerberos).

I am using this product for user authentication.

We just use the solution for the authentication and the provision access control, among other tasks.

Most of my customers use Active Directory Premium for condition and access scenarios that they need to comply with my conditions to access my resources. They also build new environments, virtual machines, and some other products like SQL on the infrastructure as a service. There are some customers that use Microsoft Intune, which is mobile device management. Microsoft Intune is a cloud.

This product manages access for our compute space that includes Office 365, Salesforce, and other solutions.

We are a software development company and solution provider, and this is one of the products that we implement for our clients. This is an easy way to give users access to applications. I can share access with other organizations outside of our network.

We use this solution to extend on-premises Active Directory to the cloud.