Microsoft Entra ID

Formerly Microsoft Azure Active Directory

There are organizations out there that are choosing not to use AD, be it on premise or cloud based like Microsoft Entra ID, but the system has been around for very long time and it is only bringing an easier management of resources, more secure environment and easier to navigate changes ahead. so this system will be giving a great ROI to them that are adapting to this tool, as it will just integrate great with other product suite like Teams, Yammer, Onedrive, Sharepoint online etc. A dedicated team needs to be managing it to ensure it is doing what it suppose to be done and it is giving the potential values it has

For those organizations that are opting out from these, The budget reason will be most likely the case, as it will not be giving the ROI where that organization is already without AD in the first place, hence the migration will be a pain process

It is well suited for creating and updating and deleting employee attributes through Azure AD provisioning. But there can be some scenarios such as installation of provisioning agent documentation can be improved with proper screenshots. This will help consultants better in further implementations in future. The integration perspective is good but still the documentation available has scope of improvement.

Microsoft Entra ID is well suited for most organizations who want a cloud based AD solution that allows administrators to manage users, spin up VMs, and integrate their internal applications with SSO. The software may not be well suited for businesses that use other softwares to do any of the tasks mentioned above, as they may not get their full money's worth.

It is very good for managing applications, especially SSO and auth parts. The RBAC can be improved

Microsoft Entra ID is specifically good where the user needs quick and easy solution for authentication and authorization capabilities in the software. It is less appropriate where the user wants to implement a solution where it doesn't want to get locked-in via a vendor for example Microsoft. Also the console may be a bit complex for first time users.

If you have more than say 10 machines to manage and 20+ users who login to these machines everyday, its tough to manage these users and servers individually so rather use Microsoft Entra ID to authenticate users and allow them access to resources or computers with restricted policies. So overall its very helpful in managing Organizational resources as the organization size increases.

It functions for hybrid environments in syncing to Microsoft 365 for email, onedrive, etc but we have a good amount of issues since they have moved over from Azure and it seems different components are constantly changing and require a fair amount of work to keep everything up to date.

Based on my experience using Microsoft Entra ID in a small business, I'd definitely recommend it for other small organizations. But I can see that it offers more features than we're currently able to take advantage of. It's obviously more tailored to large organizations, but I appreciate that it's simple to manage with a small, resource-limited team.

Scenario 1: The most obvious would be if the org. has Azure presence with or without an on-premises AD instance. Scenario 2: Even from an SSO point-of-view, Microsoft Entra ID would be a great choice to be opted as an Identity Provider. Scenario 3: If the org. has a wide global footprint and wants to ensure a secure identity and access management platform that can prevent real time attacks without compromising user experience. Scenario 4: If the org. has both B2B and B2C collaboration scenarios.

All kinds of organisations where they want to have a centralised identity, they can choose Microsoft Entra ID. We can integrate Entra ID with other clouds. Also, we can easily sync the identities to various public cloud and have a single and centralized identity. It can be implemented with ease and manage it easily.

Microsoft Entra ID provides easy management for users & groups in the cloud. We still use local Active Directory and are slowly integrating more and more with the cloud.
Currently we mainly integrate cloud solutions/applications with Microsoft Entra ID, while keeping our locally developped apps integrated with on-prem solutions.

It reduces the risk of fraud by ensuring that only authorized individuals can approve important transactions through biometric authentication. In an era of remote work, the software's MFA features have been incredibly beneficial. It allows our remote workers to securely and easily access financial systems and data from anywhere. Microsoft Entra ID is effective in controlling access, permitting only authorized individuals to view private financial data and systems.

Any organisation that wants to use any off-premise/cloud based services should be using Microsoft Entra ID to centralised authentication and security. Having the ability to disable access to ALL applications through one account/portal gives the IT team back control over security for your organisation.

it is well suite because it helps with security. The SSO and MFA are by far the best 2 features in AAD today. moving to the windows authenticator method will be a easier option moving forward since sim swapping has occurred recently

Microsoft Entra ID is a must in any office 365 environment, but it is also useful to integrate into other applications so you can offer a single SSO service to your users without any additional products. It scales well so it can easily be implemented in a business with 5 users or 1000. The features that are included are great even without paying an additional subscription, but there are a few features from a P1 subscription that add a lot of important features that will help keep users safer from attacks.

If I recommend it, the use according to our needs has been super simple; it also maintains the privacy of each user's access to the information they need to have, and it has guaranteed us superior security.

The use of Microsoft Entra ID, previously known as Azure AD, is necessary when using Microsoft 365. It can also be used for single sign-on, to link local AD to the cloud, and for implementing multifactor authentication (MFA). Using Entra ID to enforce MFA with Microsoft 365 is simple and should be considered if your organization is not already using it.

If you're already using Microsoft products, Azure tenant, O365... you will be using Entra ID. At that point, you should consider to use it as cloud identity provider, as it is really easy to use it with 3rd party applications, it has a lot of pre-built integrations, and you can apply conditional access rules, wich is a plus.
If you're not using any Microsoft products, either on-prem or on Azure... maybe it's not your best choice, as it'll be more expensive than other solutions.

Good if you're all in on the Microsoft online environment, MS365 or using Azure services. Integrates very well with those.
Not so much if you're just using it as an IDP for other services. It does try to take over somethings (like MX and DNS records) that you may want to keep having managed/hosted at 3rd parties.

If an organization is using Microsoft 365 and has the IDP license, there is no reason not to use Microsoft Entra ID. If your org uses 365 and does not have the IDP license, I recommend upgrading your licenses if your budget allows.

It is great for managing users and sign ins. We can tell where users are signing in and which devices they are using.

It well suited for scenarios where you have users accessing applications from outside of the organizational premise for example we have field force representatives that visit different locations take orders and update data on their mobiles and tablets. so, it's very easy for them to simply open the app and input required data and its automatically sync with published web application and we are managing the authentication and authorization through Entra ID and conditional access through intunes conditional access policies.

If you have many users and need to separate them into groups with access that changes based on their role or status, I think dynamic groups handles this brilliantly.

Creating a secure environment where identify and access are highly secure and authenticated is very easy to manage and user.

It also allows for various levels of administrative access. You can give certain people access to user administration without having to give them access to other administrative functions.

In my experience, there really isn’t a size or scope of company that could not benefit from Microsoft Entra ID.

It is well suited for all type of companies that want to manage users and their devices on the cloud. Easy for the administrators to manage all the users and all the devices and easy to block when one of the devices gets comprimised.