Sprememba UPN imena ni uspela v Azure AD

Sprememba UPN imena je lahko z več različnih razlogov npr. sprememba priimka, zadnje čase pa predvsem želimo lažje delo z office 365 aplikacijami, kjer Microsoft priporoča, da je UPN enak privzetemu elektronskemu naslovu. Kako pa se to naredi?

Enostavno. V Active Directory-u, ki se nahaja na on-premise, se poenoti UPN z elektronskim naslovom. Pri sinhronizaciji v Azure AD se potem spremeni tudi v oblaku.

Kar pogosto pa se zgodi, da se zalomi pri sinhronizaciji in ostane v Azure AD v veljavi še star UPN. Tu potem uporabimo powershell in popravimo, kar ni uspelo sinhronizaciji.

Set-MsolUserPrincipalName -UserPrincipalName  "prejšnji upn" -NewUserPrincipalName "nov upn"

Nato lahko v M365 Admin centru ali v Azure AD vidimo spremembo in uporabnik se lahko končno prijavi z novim UPN-jem v Microsoftov oblak.

Tako, sedaj ni več zmede za običajne uporabnike. Tudi zunanji partnerji sedaj očitno lažje pošljejo vabilo za varen dostop do SharePoint online, One Drive ali Teams.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Change UPN error in Azure AD

Changing your UPN name can be done for a number of different reasons, e.g. changing your last name. But lately, we want to work more easily with Office 365 applications, where Microsoft recommends that UPN would be the same as the default e-mail address. How to do you do that?

Set-MsolUserPrincipalName -UserPrincipalName  "current upn" -NewUserPrincipalName "new upn"

Then we can see a change in the M365 Admin Center or in Azure AD and the user can finally log on with the new UPN to the Microsoft cloud.

There is obviousily no more confusion for normal users. Even external partners now seem to be able to send an invitation for secure access to SharePoint online, One Drive or Teams

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.