Jeremy Brooks

So, I've tried to run the Invoke-pronunsync powershell, but it's still coming back Get-PnPUserProfileProperty : Attempted to perform an unauthorized operation. I've got Sharepoint Admin access, as well as global...

> Are you connecting to the nnnnn-admin.sharepoint.com site when calling Connect-PnPOnline? Yes, and it connects fine

Hi, this happens with all users, and they are sync’d from on-prem.

> Ah, got it. So the script to update the extension attribute in Azure AD will only work for cloud users. If your users are synced from on-prem you will...

Hi, Sorry I’m being a pain now. I’ve tried to change the code but it still wasn’t running correctly, hence the attached file. Just wondering, if you could take a...

@merill still getting issues trying to get this to work, with the lines commented out, I get this: At C:\pronoun\Invoke-PronounSync.ps1:52 char:79 + ... -ADUser –Identity $aadUser -add @{"extensionattribute1"="MyString"} + ~~...

Hi @CabbageandBean I've tested your script, and it's running through my directory without an issue, though I'm sure I tried what you've done, and couldn't get it to run, one...

@CabbageandBean running on a Win 22 Server, running as a DC. Even with the replace, it just scrolls through, it's like it's not reading the Pronoun field, that was setup...

When it runs through, it just shows checking, when it gets to my account, which I've amended the Pronoun in the cloud, it just shows checking

I've found out what the issue was, when I'd created the field to alter in Sharepoint, I'd called it UserPronoun, so it couldn't pick up the field, I removed that...