What is our primary use case?
During the migration, we adopted Microsoft Entra ID. From day one, we have used it for all of our MFA, Intune, and Conditional Access policies. Everything is managed by Microsoft Entra ID. We have an Azure subscription, which is also integrated with Microsoft Entra ID, and we actively use it to manage role-based access for our Azure environment through Microsoft Entra ID groups and permissions.
How has it helped my organization?
Microsoft Entra ID makes user management easy, and that is one of the big benefits I see. I don't need to jump between different platforms. For example, if you have an on-prem AD with groups, you can sync those groups to Microsoft Entra ID and manage them. If you start creating Microsoft Entra ID groups, you get a variety of group types: security groups and Microsoft 365 groups for Teams and SharePoint channels. You can also create distribution lists and dynamic distribution lists. In addition, the role-based access group is managed through our Azure platform. The good thing is that Microsoft Entra ID sits in the center. It manages our entire Microsoft 365 ecosystem and all the security tools. It manages our Copilot and our Foundry. It also manages our entire Power Platform, including Fabric and Power BI. That is one of the best things and the benefit I get from Microsoft Entra ID on a daily basis. From an administration standpoint, I think it is one of the best tools.
The biggest impact that Microsoft Entra ID has had on our secure access to apps and resources is the Conditional Access policy with Multi-Factor Authentication, which is also managed by Microsoft Entra ID. We have a very custom setup that I don't think any other organization generally uses. We have device restriction and IP restriction policies, which are also managed by Microsoft Entra ID. We created the Conditional Access policy in such a way that if anybody is going to get into a specific application, it doesn't matter whether it's Office 365 or a third-party application hosted in Azure. We always have all those applications authenticated through Microsoft Entra ID and have Conditional Access policies applied. If anybody is trying to do something from their personal device, everyone will get it. Recently, we have started adding our AI-registered agent registration as well, which is amazing. I can control the restrictions and policies, including what access the agents have and what access they don't. All these features are amazing.
Microsoft Entra ID integration capabilities have 100% influenced our Zero Trust model. Microsoft Entra ID has full integration with Purview and our Defender ecosystem, and they play the key role in our Zero Trust implementation. If anything goes wrong, Defender provides us the information and we can correct it. Automatically, 100%, it plays a role. It manages all the security. All the policies we created in Purview and Defender for Zero Trust are managed by Microsoft Entra ID rules.
Since implementing Microsoft Entra ID, we definitely see an improvement and we feel more confident, but we have never encountered any security challenges or issues specific to identity theft. That may be our luck. After moving to Microsoft Entra ID, we feel more secure because it provides us an additional layer of security with Multi-Factor Authentication, Conditional Access policies, and all the delegated permissions using Microsoft Graph API and registration. We definitely feel more confident, but we have never encountered a specific scenario where I could say, "Okay, this makes the difference," or "This incident is not going to happen because we are in Microsoft Entra ID now." We have never encountered that.
Our company's approach to defending against token theft and nation-state attacks has definitely changed since implementing Microsoft Entra ID, and we are exploring some of the options with Microsoft to advance our Microsoft Entra ID integration. Our goal is to get Intune in place. Right now, we have Intune just for personal device management. With Microsoft Entra ID integrations through MDM and Intune, if we start working on corporate device management, that is going to be a game changer, and we are planning to do that with Microsoft.
Token replay detection, attacker-in-the-middle detection, and verified threat actor IP all have an impact on our environment. All of them do.
The implementation of device-bound passkeys and Microsoft Authenticator has 100% affected our company's approach to phishing-resistant authentication.
What is most valuable?
Microsoft Entra ID as a whole is amazing, and the feature I like most is the app registration and the Microsoft Graph API concept. Many people reach out to us saying, "I want to do this integration, that integration. I need this application to be integrated." When we do those configurations and integrations using Microsoft Graph delegated permission, it restricts and controls what an app can do. The security level of control we get from Microsoft Graph API is amazing.
Second, Conditional Access policy is my personal favorite for MFA for a lot of internal applications. You can handle things elsewhere, but when it comes to security controls, I always trust Conditional Access policies, whether they involve device policies, IP restrictions, or something else.
What needs improvement?
Microsoft Entra ID can be improved in a few ways, and I definitely want to provide some recommendations. The UI for app registration and Enterprise Applications is separate. Those should be combined so that people can understand them more easily. I think Microsoft made some enhancements, such as being able to do the app registration within the Enterprise Application, but it is still very confusing when a new administrator joins my team. I always need to explain the difference between the two, so it definitely needs some work.
Some of the features on the MFA policies and the IP restrictions need improvement. In Microsoft Defender for Cloud Apps (Cloud App Security), which is a feature of Defender at security.microsoft.com, there is a connection where, if I select Zscaler, it automatically whitelists the Zscaler IP. In Microsoft Entra ID, that feature is missing. I'm surprised that one Microsoft product provides this while another product does not give me a list of companies whose IPs I can whitelist. I need to go and manually whitelist those IPs, and I don't like that at all. I think that fix is 100% needed. If it exists in Defender for Cloud Apps, how hard is it to bring it into Azure?
The only other feedback I will give is on Microsoft Entra Connect. When I do hybrid configurations from AD to Microsoft Entra ID, the biggest problem I see is that I always need to wait for the syncs, and the sync intervals do not give clear visibility of what is happening and what is not. There should be a mechanism where the administrator gets visibility of what is going on, because sometimes we have priority actions to take, and we need a way to make those syncs happen immediately so the replication happens faster. Our organization is very big, and one sync cycle takes more than one hour. We cannot wait one hour to resolve an issue when something needs to be synced from AD to the cloud.
For how long have I used the solution?
We have been using Microsoft Entra ID since 2019, when we started the merging of two different companies. We are on Office 365 for our entire organization, and both companies are on Microsoft 365.
What do I think about the stability of the solution?
In my assessment of the stability and reliability of Microsoft Entra ID, I have never seen any specific outage. There are different products integrated with Microsoft Entra ID that have had outages.
How are customer service and support?
If I evaluate Microsoft support, I would rate them four out of five.
On a scale of one to ten, I would rate Microsoft support an eight. I am taking two points off because a couple of incidents happened with us in the past where we received very poor support. It has improved. If I contact my client engagement person, he helps me a lot, and he is amazing. However, if I don't contact anybody in Microsoft directly and instead open a general ticket, I don't like the support. I always like the support when I reach out to somebody else, such as my account rep, and then get support in a different way. There should not be a difference between an engineer directly raising a ticket and me, as a manager, reaching out to people in Microsoft. There should not be a difference, and I don't like that.
Which solution did I use previously and why did I switch?
Before Microsoft Entra ID, we relied on Active Directory and ADFS for application authentication management. We also had the RSA MFA token. We have eliminated RSA and ADFS after moving everything to Microsoft Entra ID.
How was the initial setup?
My experience deploying Microsoft Entra ID is good. It is not the first time I have done an Office 365 and Microsoft Entra ID implementation. In my career, I have done it at least four to five times. Every time, I get a different experience because Microsoft makes it more automated, with a more single-click implementation instead of doing manual work. I like that. Every year, it is improving.
What about the implementation team?
I was involved in the deployment of Microsoft Entra ID, and I personally deployed it in 2019.
What was our ROI?
In terms of return on investment, I will not say Microsoft Entra ID reduced the cost, because ADFS and Active Directory are an on-premise Microsoft ecosystem. We just eliminated the administration of the servers. We eliminated a lot of servers that required patching and a lot of manual work. That was eliminated because everything is now managed through Microsoft Entra ID.
Our user base is very high. We have close to 25,000 accounts within Microsoft Entra ID. From that point of view, a lot of administration would be required if we had it on AD and ADFS with application management. We have at least 600+ applications that were earlier integrated with ADFS, and we have moved them to Microsoft Entra ID.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup costs, and licensing for Microsoft Entra ID has been positive. I never felt anything bad about the pricing because we are always on Microsoft 365 E3 for other reasons, and that includes the Microsoft Entra Premium P1 license. I never have the conversation, "Why do we need Microsoft Entra ID?" It is always there, and we are just using it.
Which other solutions did I evaluate?
We have considered other solutions, including Okta. In federation, we reviewed a couple of solutions, but the only reason we went with Microsoft Entra ID is that we are already on Microsoft 365 and have the Entra Premium P1 license for the entire company. It makes more sense within the environment. Why have an additional authentication layer instead of keeping the same one?
What other advice do I have?
On a scale of one to ten, I would rate Microsoft Entra ID 100%, a ten, because it solves your identity problem. It solves your administration challenges. You have the most automation you can get. You know you are 100% secure if you are dealing within Microsoft Entra ID. There are other tools, such as Okta or other identity platforms, that you can use to be secure, but Microsoft Entra ID is part of your Microsoft ecosystem. If any organization is on Microsoft 365, it should not think about any product other than Microsoft Entra ID. It should only choose Microsoft Entra ID as its product. That is what I feel, and that is why I feel it is one of the best.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure