Your network contains an Active Directory forest. The forest contains two domains named contoso.com and adatum.com.
Your company recently purchased a Microsoft 365 subscription.
You deploy a federated identity solution to the environment.
You use the following command to configure contoso.com for federation.
Convert-MsolDomaintoFederated CDomainName contoso.com
In the Microsoft 365 tenant, an administrator adds and verifies the adatum.com domain name.
You need to configure the adatum.com Active Directory domain for federated authentication.
Which two actions should you perform before you run the Azure AD Connect wizard? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.
A . From Windows PowerShell, run the Convert-MsolDomaintoFederated CDomainName contoso.com CSupportMultipleDomain command.
B . From Windows PowerShell, run the New-MsolFederatedDomain
CSupportMultipleDomain -DomainName contoso.com command.
C . From Windows PowerShell, run the New-MsolFederatedDomain -DomainName adatum.com command.
D . From Windows PowerShell, run the Update-MSOLFederatedDomain CDomainName contoso.com CSupportMultipleDomain command.
E . From the federation server, remove the Microsoft Office 365 relying party trust.
Answer: A,E
Explanation:
When the Convert-MsolDomaintoFederated CDomainName contoso.com command was run, a relying party trust was created.
Adding a second domain (adatum.com in this case) will only work if the SupportMultipleDomain switch was used when the initial federation was configured by running the Convert-MsolDomaintoFederated CDomainName contoso.com command.
Therefore, we need to start again by removing the relying party trust then running the Convert-MsolDomaintoFederated command again with the SupportMultipleDomain switch.
Latest MS-100 Dumps Valid Version with 297 Q&As
Latest And Valid Q&A | Instant Download | Once Fail, Full Refund