A company has an Office 365 tenant that has an Enterprise E1 subscription. You configure the
policies required for self-service password reset.
You need to ensure that all existing users can perform self-service password resets.
Which Windows PowerShell cmdlet should you run?
A.
Set-MsolUser
B.
Redo-MsolProvisionUser
C.
Set-MsolUserLicense
D.
Set-MsolUserPrincipalName
E.
Convert-MsolFederatedUser
F.
Set-MailUser
G.
Set-LinkedUser
H.
New-MsolUser
Explanation:
Self-service password reset with on-premises write-back is a Premium-only feature.
Example:
The following command adds the Office 365 for enterprises license to the user.
Set-MsolUserLicense -UserPrincipalName [email protected] -AddLicenses
“Contoso:ENTERPRISEPACK”
Note: The Set-MsolUserLicense cmdlet can be used to adjust the licenses for a user. This can include
adding a new license, removing a license, updating the license options, or any combination of these
actions.
Incorrect answers:
Not A: The Set-MsolUser cmdlet is used to update a user object. This cmdlet should be used for basic
properties only. The licenses, password, and User Principal Name for a user can be updated through
the Set-MsolUserLicense, Set-MsolUserPassword, and Set-MsolUserPrincipalName cmdlets
respectively.
Not B: The Redo-MsolProvisionUser cmdlet can be used to retry the provisioning of a user object in
Azure Active Directory when a previous attempt to create the user object resulted in a validation
error.
Not C: Not D: The Set-MsolUserPrincipalName cmdlet is used to change the User Principal Name
(user ID) of a user. This cmdlet can be used to move a user between a federated and standard
domain, which will result in their authentication type changing to that of the target domain.
Not E: The Convert-MsolFederatedUser cmdlet is used to update a user in a domain that was
recently converted from single sign-on (also known as identity federation) to standard
authentication type.
Not F: Use the Set-MailUser cmdlet to modify the mail-related attributes of an existing user in Active
Directory.
This cmdlet is available in on-premises Exchange Server 2013 and in the cloud-based service.
Not G: Use the Set-LinkedUser cmdlet to modify the properties of a linked user account. A linked
user is an account in one organization that is associated with an account in a different organization.
Not H: The New-MsolUser cmdlet is used to create a new user in the Microsoft Azure Active
Directory (Microsoft Azure AD).Set-MsolUserLicense
https://msdn.microsoft.com/en-us/library/azure/dn194094.aspx
Can confirm that someone?
Self-service password reset with on-premises write-back is a Premium-only feature.
Example:
The following command adds the Office 365 for enterprises license to the user.
Set-MsolUserLicense -UserPrincipalName [email protected] -AddLicenses
“Contoso:ENTERPRISEPACK”
Note: The Set-MsolUserLicense cmdlet can be used to adjust the licenses for a user.
This can include adding a new license, removing a license, updating the license options, or any
combination of these actions.
Reference: Set-MsolUserLicense
https://msdn.microsoft.com/en-us/library/azure/dn194094.aspx
Apparently self-service password reset is included in all office 365 subscriptions. I can’t find a command that enables it, only how to enable it using Azure.
Dodgy question maybe?
Looks like you can add Azure AD licenses with Set-MsolUserLicense – so I’ll opt for C as well. As most sources suggest you need Azure Premium for Self Service Password reset.
NEW QUESTIONS IN 70-346:
Note This question is part of a series of questions that present the same scenario Each question in the series contains a unique solution. Determine whether the solution meets the stated goals.
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 netdom.com command.
Does the meet the goal?
A. YES
B. NO
Note This question is part of a series of questions that present the same scenario Each question in the series contains a unique solution. Determine whether the solution meets the stated goals.
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 the meet the goal?
A. YES
B. NO
Note This question is part of a series of questions that present the same scenario Each question in the series contains a unique solution. Determine whether the solution meets the stated goals.
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-MsolFederatedDomain cmdlet.
Does the meet the goal?
A. YES
B. NO
CAN YOU PLEASE PUT THE CORRECT ANSWERS FOR THESE QUESTIONS?
Netdom.com –> NO
New-MsolDomain –> NO
New-MsolFederatedDomain –> YES
Note
Once you have used the New-MsolFederatedDomain cmdlet to add a top-level domain you will not be able to use the New-MsolDomain cmdlet to add standard domains (non-federated).
Set up a trust between AD FS and Azure AD
https://msdn.microsoft.com/en-us/library/azure/jj205461.aspx
https://technet.microsoft.com/en-us/library/jj205461.aspx