Microsoft Entra ID

Formerly Microsoft Azure Active Directory

Microsoft Entra ID (formerly Azure) is a great product that we utilize for deploying VMs, integrating SSO within applications, managing users, groups, and inboxes, and more. While the online software is not always intuitive for administrators to use (the UI changes frequently) and the name change caused a great amount of confusion, the product is solid, mature, and most of all does the job in all the categories mentioned above.

We use Microsoft Entra for Hybrid cloud functionality. Our local domain syncs with Microsoft services for email and applications

We use Microsoft Entra ID to provide authentication & authorization to our end users for all cloud solutions that are used within the company. It provides easy single sign-on capabilities to a lot of enterprise applications.

Probably the best known tool for Active Directory management. Integrates with just about any other online software that needs an ID provider (as it's so well known). Not always the easiest to set up or use at times, but the support documentation is good and online community is very large. Useful for managing security, and identity of staff and guest users to our systems.

We have been using Microsoft 365 (formerly Office 365) for more than five years. We have used Microsoft 365 Identity Protection (now known as Microsoft Entra ID) for three years.

In my org we use Microsoft Entra ID for security and ease of access for our users. First, we deployed self-service password reset to all of our users, which required they enter some additional information like personal contact info. This required some training on our part to let everyone know what was happening. Then, multi factor authentication and the Microsoft Authenticator provide protection. Once we had deployed MFA and had 100% adoption, we introduced phone sign-on so users did not need to use passwords when signing in.

We have also implemented conditional access to require MFA for all apps, and to block access if certain thresholds are met for failed sign-ins or unusual activity.

We need to manage many discreet groups of people and their access to systems and licensing base on multiple criteria. We have staff who are various kinds of employees as well as volunteers. In addition to our staff/volunteers we also have associates that are involved but do not need the full spectrum of Microsoft 365 services. Additionally we have an intranet and hundreds of teams that need access permissions based on identity. A tool like Microsoft Entra ID is essential to managing this successfully.

We have migrated all of our systems to Entra ID for SSO. It provides a single point of sign-on for users while also providing multifactor authentication for security. Users are now able to reset their own passwords(previously, they would have to call the help desk), and we have better insight into where users are signing in from and also which accounts are being attacked by unknown third parties.

Incident response, vulnerability management, as in configuration assessment, hardening and threat hunting.

I help administer the identity use cases for Microsoft Entra ID. We use it as our primary identity in a hybrid configuration with our on-prem Active Directory. This also provides the base for our Office 365 products.

We use Microsoft Entra ID to manage Users, groups and resources in our organisation. We have been using Azure AD for a longer time and now because of the name change its Microsoft Entra ID. The Microsoft Entra ID is a great way to manage all your resources in a particular tenant. This is easily accessible from any device using 2 FA

We use Microsoft Entra ID for our users when accessing company applications and services and it allows seamless SSO authentication. We've also incorporated authentication with several Software as a Service (SaaS) applications, providing a centralized approach to identity management. We have also implemented multi-factor authentication using Microsoft Entra ID.

We currently use Microsoft Entra ID (Azure Active Directory) for several of our companies, some are hybrid and some are Entra only. Entra provides us with a trusted and proven directory solution that works well with our other suites (such as M365) since they are all Microsoft products. With Entra, we have the flexibility to support our existing configurations (on-prem AD) while also providing support for our newest configurations (Cloud-only).

Microsoft Azure Active Directory is used to control access to our apps and app resources. Management of Microsoft licenses (Office, OS, ..), setup of MFA authentication and a lot more

An active directory is like the number one must-have software that any organization should have if they are using windows based operating system. With windows operating system, Azure active directory is "the" go to software that any organization should invest in. Azure active directory comes from their original on premise active directory software so the program has years of experience on the field. I started using windows active directory back in 2003 and when azure active directory service came on it was a no brainer decision to migrate from on-premise solution to cloud. The product primarily address user authentication, file sharing, Document management (Share point) Office tools access like MS suite etc. We cannot work without an active directory in this day and age where hybrid and remote work is the preferred solution. The software also tightly integrates with almost all business ERP solutions like SAP, Oracle MS Sql etc. So you don’t need to maintain a third party tool for access control to these software’s. They also work with your exchange services so that it makes our onboarding of new users a breeze.

Microsoft Azure Active Directory is the key component of our identity, authentication, and authorization strategy. It is fully integrated with our HR platform for onboarding and separation and enables Single-sign-on, muti-factor-authentication, and a host of other basic and advanced identity-related services. Using all that Microsoft has to offer in this space simplifies our environment and makes additional third-party products specifically targeting identity management unnecessary.

We purchased the Office 365 A5 suite about three years ago. We use Microsoft Azure Active Directory across our entire district for 30,000+ users. This is what we use to help manage our users.

Across the whole organization - globally in US, Asia and Europe

Our Microsoft Azure Active Directory helps us manage all of our users including their metadata. It is used across all of our organization, helping us manage and maintain our departments employees and machines. Essentially, we use it as a central management tool that connects all our software and tools with our users and machines database.

[Microsoft] Azure Active Directory is currently used to replicate our on premise Active Directory. We use this across the organization to enable single sign-on to other Microsoft services including office 365, and our home grown web applications.

Azure Active Directory is being used across the entire organization. Azure AD allows us to manage access/permissions for various applications, resources, etc.

We are service provider and an ISV, we build and customize software and deliver IT Solutions to our customers, we needed an identity and access management solution that is widely compatible with our application infrastructure as well as allows us to integrate content across tenants, we also wanted a unified and simplified IAM experience for our internal users, our customers and contractors.

AzureAD was definately the optimial option, it allowed us to unify our IT administration experience through tightly integrated capabilities, and simplified synchronization of objects from On-Premises Active Directory, additionally, most of our online services for internal users are on Microsoft 365, in such scenarios, AzureAD is absolutly the best choice for our organization.

It scaled nicely as the company grows, and offers RBAC, Conditional Access and Privileged Identity Management, it also supports most of the common authentication scenarios and protocols that we require in our business, we are very much satisfied with how AzureAD works and it is definately a reliable and flexible IAM solution.

Our organization uses Azure AD for verification across all platforms. But not only that, I also implement ERP software based on Microsoft Dynamics 365 Business Central and integrate it with Azure AD for customers. The Azure administrator of the customers create an app registration, which I then use in Business Central for integration. That way the users of our customers can use their Office 365 credentials to access Business Central. For the app registration to work well, I have to work with the customers system administrator. The app registration has to be set up thoroughly for it to work well with Business Central.

Azure Active Directory is being used in conjunction with our SharePoint 360 environment to manage users from multiple functional areas of our company. We use it store user information as well as their access levels. Any changes to the settings in Azure Active Directory reflects the user's permission levels across multiple platforms on our network.

We use M365 within our school district, and as such, Microsoft Azure Active Directory is our cloud identity provider for all our user accounts (faculty, staff, and students). Ultimately, we are a hybrid Microsoft Azure Active Directory environment, with an on-prem Active Directory that syncs to local objects to Azure. This synchronization helps address the need for cloud-based access to resources that would otherwise be unavailable if we were solely working from an on-prem Microsoft Azure Active Directory environment. We have considered moving all our users and devices to being 100% cloud based; however, the current Microsoft Azure Active Directory infrastructure we are a part of (multi-domain forest) is not currently suited to support that transition at this time.

We are working with a health care client to handle their CRM software in the cloud. Our company is using Microsoft Azure Active Directory for the database workload and also for their third-party API with client data transitions (so it is being used by only the Database management department for now).

We are using Microsoft Azure Active Directory for basic operations:

• Single sign-on, enabling access to apps from anywhere
• Conditional access and multi-factor authentication to help protect and govern access over the users
• Integrating identities with other apps and authenticating for the work system