Microsoft Entra External ID Reviews

I have been dealing with the security part for sure.

The fact that it is quite integrated into the entire Microsoft environment makes it quite easy to use. 

Furthermore, Microsoft's reliability in providing a clear roadmap for the solution is very important, especially at a time when cybersecurity is a risk in every company. 

The solution is easy to reuse and not difficult to find expertise for in the market because it is widespread. 

It is gaining attention even from partners and from the market on the offering side. This serves as a good starting point for customers who can develop internal competence on the solution. 

Additionally, the presence of reliable partners who know the solution and can provide internal knowledge is the best aspect for them.

I use Microsoft Entra external ID for enterprise purposes, particularly for Microsoft Teams.

The most valuable feature for me is the firewall capabilities. Additionally, the single sign-on feature is very useful as a single solution can be used for multiple types of single sign-on applications. This helps in cost as well as time saving since I can use a single solution for all the applications.

I am working on a project for a university where we are trying to create a digital twin of a coral reef restoration project in Saudi Arabia. This involves using a big data platform and developing a mobile web application for research purposes. As part of the project, we are widely using data analytics tools, data fabric, data lake, and other Azure services.

The most impactful feature of Microsoft Entra External ID for access management needs is the federated identities, which allows us to use single sign-on with different federated logins. This feature is valuable because many companies prefer to have a single sign-on solution. Additionally, integration using federated authentication or token keys is possible. However, I am not well-versed in the governance part. In our current setup, the initial setup process for Microsoft Entra External ID is based on the use case, and it is generally straightforward for simple tasks like user creation and management. However, it can become complex depending on the project requirements.

It is for Office 365, and then for Exchange server. It's for the Entra, and then to link up with Okta.

My company, as well as my customers, use it. 

It is easy to onboard users and it's easy to manage.

The security controls in Entra ID are quite okay because they integrate for ID authentication. We need that; they're secure. If it's not integrated with another solution, meaning that it's not secure, it's okay. It's quite secure for me because you're all integrated.

We use Microsoft Entra External ID for cross-company collaboration by importing applications through enterprise applications. Most applications have APIs that easily connect to Azure. We generate a token, ID, and key, which we input into the application server to link them. This allows our AD users to connect to these applications.

The most beneficial feature for us is the ease of setup. With about five clicks, we can generate unique IDs and keys and set up in less than 30 minutes. We can also generate these for multiple years simultaneously, which is convenient.

In Azure, you can set up access rules. Just because an app is linked to Active Directory doesn’t mean everyone can access it automatically. You can make it so users have to give consent before getting access. You can also control which apps can connect to Active Directory. For Microsoft Exchange, we use multi-factor authentication to protect our information, which helps keep it secure by requiring more than just a password to log in.

Centralizing user management has positively impacted our operational costs and efficiency. We no longer need multiple systems to manage users, especially in our SaaS applications. This has improved turnaround time for user management tasks and streamlined our processes, making things more efficient.

We use the SaaS version, so there's no on-premises infrastructure. The integration is mainly done through setup, linking it to our domain and Active Directory.

We had a project to integrate our Active Directory, which was running on our site, and invite external collaborators, such as freelancers, to connect to our domain via an invitation. Additionally, we merged with another company, which involved integrating both domains. 

It's similar to using a Microsoft account to create accounts on other websites. We are also using Microsoft Entra to monitor which applications our guests are using. This allows us to filter, block, or adjust permissions for these applications as needed for our collaborators.