Note: This question is part of a series of questions that present the same scenario. Each question in the series
contains a unique solution that might meet the stated goals. Some question sets might have more than one
correct solution, while others might not have a correct solution.
After you answer a question in this sections, you will NOT be able to return to it. As a result, these questions will
not appear in the review screen.
You have an on-premises Active Directory forest.
You deploy Active Directory Federation Services (AD FS) and purchase an Office 365 subscription.
You need to create a trust between the AD FS servers and the Office 365 subscription.
Solution: You run the New-MsolDomain cmdlet.
Does this meet the goal?
A.
Yes
B.
No
Explanation:
The New-MsolDomain cmdlet adds a domain to Azure Active Directory.
The New-MsolFederatedDomain command should be used instead.
Note: The New-MsolFederatedDomain cmdlet adds a new single sign-on domain to Microsoft Online Services
and configures the relying party trust settings between the on-premises Active Directory Federation Services
2.0 server and Microsoft Online.
https://docs.microsoft.com/en-us/powershell/msonline/v1/new-msolfederateddomain
Wrong, you need to add à domain before you can federate it. It does mention you bought à subscription, but not added à custom domain yet.
You deploy Active Directory Federation Services (AD FS) and purchase an Office 365 subscription.
You need to create a trust between the AD FS servers and the Office 365 subscription.
It does however specifically say that you need to create a trust between the AD FS servers and the Office 365 **subscription**
So I’m guessing the shown answer to this question is the right one.
Correct
Question is You need to create a trust between the AD FS servers and the Office 365 subscription, so even first thing we have to do run the New-MsolDomain cmdlet but still it will not create any trust between AD FS servers and the Office 365