Cloud Consultant at a tech vendor with 11-50 employees
Consultant
2018-11-12T09:12:00Z
Nov 12, 2018
We need it for running MSA protection for most of the users. We need Azure AD Connect because they are highly on primary setup, so they need to sync on primary with Azure AD.
The primary use case is actually one interesting one because this customer we're deploying, They don't have Active Directory on-premise, and they need to use some applications that are on-prem, so in order to get authentication to work with those applications we had to come up with a workaround. So it was challenging to come up with that workaround and solution, but it worked quite well. Azure Ad provides great flexibility even when nothing on-prem can provide user authentication. For cases like this, Microsoft and Citrix worked together to develop a solution that not only work with Azure AD but with other Directory tools to provide authentication via SAML or OAuth.
The primary use case is collaboration. So it's all about federation of identity and permissions. Identity is one of those things that you need to be separate from your actual tenant. There's a benefit for it being separated from your actual tenant for reasons of security and containerization. It's very easy to run and it's part of their ecosystem and I don't think it's going anywhere anytime soon.
The primary use case of this solution is single sign-on, and if a company is going to use Azure AD, a lot of what they are looking for is to manage those sign-ins and logins and have a single place for it to be.
Senior Technical Consultant at a tech services company with 51-200 employees
Consultant
2018-11-11T13:13:00Z
Nov 11, 2018
I primarily use this solution for hybrid deployment, security, securing resources and for integration purposes. In terms of security, we have been using the B2B/B2C hybrid integration with the certificate authentication.
Senior Analyst - IT Development at EMC Corporation
Real User
2018-10-28T09:34:00Z
Oct 28, 2018
It's a very good solution. You can manage your entity's enterprise identity using Azure Active Directory, and again, you can do several administrative activities. You can also use your Power Shares sorting and interfacing the endpoint.
Principle consultant at Active Data Consulting Services Pty Ltd
Real User
2018-10-28T09:34:00Z
Oct 28, 2018
Our primary use case is to simplify directory deployment and centralize source of management. Within our own consulting business, we choose to use Azure AD.
Microsoft Entra ID is used for extending on-premises Active Directory to the cloud, managing application access, enabling multi-factor authentication, and single sign-on. It facilitates policy enforcement and secure access, ensuring centralized identity management across cloud and on-premises resources.
Organizations utilize Microsoft Entra ID for robust user and group management, identity synchronization, and conditional access. Its seamless integration with third-party apps,...
We use this solution to extend on-premises Active Directory to the cloud.
* Office 365 authentication * SSO for ServiceNow * SSO for other cloud applications.
We need it for running MSA protection for most of the users. We need Azure AD Connect because they are highly on primary setup, so they need to sync on primary with Azure AD.
The primary use case is actually one interesting one because this customer we're deploying, They don't have Active Directory on-premise, and they need to use some applications that are on-prem, so in order to get authentication to work with those applications we had to come up with a workaround. So it was challenging to come up with that workaround and solution, but it worked quite well. Azure Ad provides great flexibility even when nothing on-prem can provide user authentication. For cases like this, Microsoft and Citrix worked together to develop a solution that not only work with Azure AD but with other Directory tools to provide authentication via SAML or OAuth.
The primary use case is collaboration. So it's all about federation of identity and permissions. Identity is one of those things that you need to be separate from your actual tenant. There's a benefit for it being separated from your actual tenant for reasons of security and containerization. It's very easy to run and it's part of their ecosystem and I don't think it's going anywhere anytime soon.
My primary use case is for our business directory, we have integrated everything into Azure into the Active Directory.
The primary use case of this solution is single sign-on, and if a company is going to use Azure AD, a lot of what they are looking for is to manage those sign-ins and logins and have a single place for it to be.
I primarily use this solution for hybrid deployment, security, securing resources and for integration purposes. In terms of security, we have been using the B2B/B2C hybrid integration with the certificate authentication.
We primarily use this solution for tracking authentication.
It's a very good solution. You can manage your entity's enterprise identity using Azure Active Directory, and again, you can do several administrative activities. You can also use your Power Shares sorting and interfacing the endpoint.
Our primary use case is to simplify directory deployment and centralize source of management. Within our own consulting business, we choose to use Azure AD.