Pros and Cons of Microsoft Entra ID 2024 (2024)

We have used Microsoft Entra ID to secure the Salesforce platform where we have data in the cloud that is quite essential for our company.

Mailchimp, Salesforce, Zendesk, Dropbox.

As our teams work in an Hybrid environment, we have identities managed on Cloud deployment, with a sub-set of identities on premises using AD. Most of the user accounts are cloud based to ensure users have access to our resources from all over the world. We have implemented conditional access …

Yes to some extent. We have configured SSO for our non-microsoft apps to provide easy and secure access. We also manage many apps like Salesforce, Slack and some of our internal build software with SAML or 0Auth.

I think at first, users just will be confused with what they see. It was a single sign on, but after the deployment and they are used to it, I think no problem at all.

Yes, we're a hybrid deployment, so we have both. We have some workers that live exclusively as cloud users and again, it verifies them access to our Microsoft data and verifies who they are when they're not in an office.

No. I mean they were already used to some other MFA tools.

We are hybrid, so we use active directory on-Prem. So we also use Entra ID on the cloud.

That I don't handle, so I wouldn't know how to answer that area.

We did. We were hybrid up until just a couple months ago. We had an onsite on-Prem active directory that we were syncing with Entra ID. We did away with that onsite because it was causing us with syncing and trying to get user data and passwords and stuff syncing properly. So we're done with that. …

Yes. We use SSO for most of the core products we use like Adobe's Product Suite, zoom robin, which is a hoteling station, like a desk reservation system. Most of the other core systems that we use.

Getting rid of on-prem was the significant change. Enabling and disabling users offboarding is significantly easier. Without the on-prem version, you can have the microphone back too.

We are just in the cloud in the last two months we have completely moved away from on-Prem.

There are customers who has both on-prem AD as well as the Azure Andra, where they have Azure Ready Connect to integrate or sync up their data and it has been worked out very well for them. And there are multiple sync problems that we have recorded and solved for them. It has been a good going so …

Entra ID has been always very successful and the user experience is definitely good when it comes to single sign-on and Entra ID has been a great product altogether.

We're entirely Cloud-based. No on-prem at all. We started with 365 and expanded it as I mentioned to other apps.

Yeah, they changed it so that they made the app first, so we noticed when that change made.

We have both internal active directory, which is connected and provisioning to our Entra id.

Yes, so we have many enterprise applications, which we provide the access to them through the Entra ID.

Non on-premise apps, but we have SaaS apps like Salesforce that are connected to the id.

I haven't noticed any changes because it was the primary tool that we were using for a couple of years now, so it was before my time.

We have an identity on-prem and we sync to the cloud as well.

Both identities i have. Just need to sync on premises with cloud using Azure AD Connect.and need to add dns for domain configuration. Like Aname, Cname and mx record for cloud sync with domain name. Hybrid deployment is at our company's promises.single login credential for both so easy for …

Yes, some positive changes at user experiences are availability of data regardless of location and device, MFA and negative impact users interact with their applications and manage their credentials, leading to some initial disruptions. and Single Sign-On (SSO) and self-service password reset.

We have a mixed enviroment, working both with on premise appliances and also cloud services. We try to use the best part of the cloud deployment, such as conditional access, mfa, high availability, etc... to use it both on cloud solutions, 3rd party integrations and on premise applications. It can …

As said before, we use it for Microsoft apps but also for 3rd party apps. It does not matter if the application is on premise or in cloud, it should be easy to integrate it with Entra ID as identity provider (we have do it with many applications) and take advantage of the feature that it offers

Yes,…

You will have to "teach" users to get used to the new login page, as they will be moved from their classic login screen to the Entra ID login page, so if you don't tell them, it will be weird for them.
Also, if you didn't have it before, multi factor auth is a plus, but it should be also showed to …

I have Microsoft Entra ID to get the access to azure cloud and few on-premises application in my organization. Its helps in securely get into the servers and do my work. Sometimes, while deployment of some cloud projects, Azure Active Directory Integration we do. It basically provides high …

I do not use this to secure any such applications.

I have connected Microsoft Entra ID with the Microsoft cloud apps like Azure Dynamics and Microsoft Office 365. Also used it in on-premises applications like LDAP to Active directory integration.

After deployment of Microsoft Entra ID, we do not need to enter our credentials for each application, through this we can directory login to the company portal through the ID and can access any application we want. The security has been enhanced because it discards the unauthorized accesses. Also …

Yes, we are using it first on-prem, then we migrate it on Azure AD. For migration from local to the cloud, we need to Add a DNS record for sync with the cloud. MX record, A record, CNAME. Domain provider needs to setup some record for migration of on-prem to cloud. application on on-prem is also …

Performance is very fast. User friendly for all users to use any o365 application. Consistency while using it. Security and authentication methods are easy to use after giving training for a time.

As far as I know, this is based on cloud at least for our Service Desk team.
We got to the portal.azure.com website for our company and use the product from there. So I guess the deployment is on cloud.
And the license I have for Microsoft Entra ID is P2.

I think the experience has been great after moving to Microsoft Entra ID, and same goes for the deployment as well.

We have used local Active Directory for decades and found a disconnect as we began utilizing more cloud-based services. Management of user accounts for disparate systems became increasingly frustrating not only for admins but also for end users who had separate logins for each. Utilizing Entra …

We do not currently use Entra ID with non-Microsoft apps.

Currently, we use Entra ID to connect with only Microsoft-based SaaS applications but look forward to more of our SaaS application vendors offering the Entra ID as an option.

The ability to use single sign-on between SaaS applications has improved our end-user experience. This will gain in popularity as more non-Microsoft applications add support for Entra ID. In addition, enforcing multifactor authentication, which could be daunting for end-users, was a simple process …

At the company I work at now, our identity is managed exclusively in the cloud. We have all user management and VMs hosted through Microsoft, not internally. We utilize the full Microsoft cloud suite for SSO, user management, and VM deployment. We utilize Intune in the cloud for device MDM and …

Yes, we utilize Entra ID to secure non-Microsoft applications. This is done by eliminating additional password requirements for the end users and having them use Microsoft's SSO system which reduces password forgetting and additional weak passwords for vendors that may not have as strict password …

During the deployment of Entra ID we noticed that end users are much more receptive to the application SSO portal than originally thought. They enjoy portal that allows usage of all relevant applications with one username and password. Productivity has been up for IT staff and end users as …

We use Active Directory for our underlying identity and integrate Entra ID into that. We have on-prem data centers as well as public cloud configurations using these technologies to underpin our identity.

We use Entra ID as our primary means of integrating our identity with many products, both legacy on-prem as well as other cloud SaaS solutions. This allows SSO and Multifactor abilities to monitor and protect.

Cloud products like Workday and Salesforce work well with Entra ID as well as on-prem …

User experience is streamlined by the use of Entra ID to protect our applications and provide SSO features that users expect.

We still have some on-prem Active Directory for some obscure functionality we cannot yet get in the cloud.

We use Entra ID for SSO for any app that we can integrate with. Most apps can.

I have not noticed any changes to the end-user experience other than those I expected to receive.

We have both an onsite server running the cloud provisioning agent and cloud identities. Our onsite server syncs with the Entra ID to provide single sign on for Microsoft services. This allows us to use a single password for signing in to on premise resources as well as cloud resources such as …

We have not configured Entra ID for non microsoft applications.

None

There have been some changes since they moved from Azure AD. There are inconsistencies in the interface from what we were originally familiar with in Azure AD. Microsoft has changed the location of several items and we have been overall disappointed with the transition and functionality of Entra …

All of our identities are in the cloud. I wouldn't really consider maintaining our credentials and managing these systems on-prem, at this point. I'd rather rely on Microsoft Entra ID to house our data securely and reliably, than try to do it ourselves. Happy to outsource as many of our IT …

Yes, we use Microsoft Entra ID to manage access to an electronic quality management system.

Yes, our users are happy about being able to quickly and easily login to multiple MS apps and SAAS apps with a single set of credentials. It definitely saves time.

Onprem Identities which gets synced to Azure Cloud via Azure AD AD-Connect. We have multiple domain controllers in multiple locations so identities in On-prem gets replicated across all DCs and then they gets synced to cloud via Azure AD connect agent. So Hybrid model of deployment is what we have.

We are a holdings company that has approximately 30 companies under our umbrella. Some of our companies are using an on-prem (hybrid) domain and some are cloud-only. The intent is to move all of our companies to cloud-only in the near future, but in the meantime Entra provides us the flexibility …

Yes, we currently have implemented Meraki sign-ins into Entra ID. This enables us to leverage security groups to grant access to the administration portal for the Meraki devices. This application shows up when a user logs into their M365 dashboard (after the app has been assigned to them). They …

As with any change that gets implemented, end users will typically have an adjustment period. I believe that inherently people don't like change, so adoption of new products/processes can cause confusion or frustrations. Overall, we had some initial grumblings about changes to the sign-in process, …