Posted on Apr 20, 2017 in IT Nerd Blog by stoff 0 Comments
SCENARIO
You’re changing the e-mail domain of a user or even a bunch of users. After that you also need to set their UPN’s to reflect the change.
PROBLEM
The problem is that Azure AD Connect service doesn’t currently support changing domain of a UPN of an object that is already synced! So you have to run a powershell command to change it. But it get’s even more complicated because you can’t change the UPN from one federated domain to another without making it “unfederated” first.
SOLUTION
Enter New-MSOLUserPrincipalName, which is a function that will take the user with the current UPN ($UserPrincipalName), change it to a temporary UPN with the domain extension “@[your tenant].onmicrosoft.com” and change it to the new UPN ($NewUserPrincipalName).
function New-MSOLUserPrincipalName { param ( $UserPrincipalName, $NewUserPrincipalName ) $TempUPN = "{0}@[your tenantname].onmicrosoft.com" -f $UserPrincipalName.split("@") Set-MsolUserPrincipalName -UserPrincipalName $UserPrincipalName -NewUserPrincipalName $TempUPN | Out-Null Set-MsolUserPrincipalName -UserPrincipalName $TempUPN -NewUserPrincipalName $NewUserPrincipalName Write-Output -InputObject "Successfully changed UPN from $UserPrincipalName to $NewUserPrincipalName" }
Thanx to Johan Dahlbom for this one!
Tags: AD FS, ADFS, Azure AD, O365, Office 365
stoff
Copyright © 2014
You must be logged in to post a comment.