QUESTION 9
: You configure Azure AD Connect for Azure Active Directory Seamless Single Sign-On (Azure AD Seamless
SSO) for an on-premises network.
Users report that when they attempt to access myapps.microsoft.com, they are prompted multiple times to sign
in and are forced to use an account name that ends with onmicrosoft.com.
You discover that there is a UPN mismatch between Azure AD and the on-premises Active Directory.
You need to ensure that the users can use single-sign on (SSO) to access Azure resources.
What should you do first?
A. From on-premises network, deploy Active Directory Federation Services (AD FS).
B. From Azure AD, add and verify a custom domain name.
C. From on-premises network, request a new certificate that contains the Active Directory domain name.
D. From the server that runs Azure AD Connect, modify the filtering options.
########################
Explanation:
Explanation:
Every new Azure AD tenant comes with an initial domain name, domainname.onmicrosoft.com. You can't
change or delete the initial domain name, but you can add your organization's names to the list. Adding
custom domain names helps you to create user names that are familiar to your users, such as
alain@contoso.com.
Only Global Administrator can create a tenant and additional Administrators. After creating your directory, you can add your custom domain name.
- Sign in to the Azure portal by using Global administrator credentials for the directory.Search for and select Azure Active Directory from any page. Then select Custom domain names > Add custom domain.
- In Custom domain name, enter your organization's new name, in this example, example.com. Select Add domain button and unverified domain for your company will be added.
- Your domain will be verified after adding txt record in your dns. After verifying your dns record you need to click button in example.com and your domain will be verified.
https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/add-custom-domain
No comments:
Post a Comment