Solved

After Recent AD Sync to Azure, Cannot Manage Exchange Online Accounts

Posted on 2016-07-22
2
471 Views
Last Modified: 2016-07-25
We just recently sync'ed our AD domain with Exchange Online. Our Exchange had been migrated over a year ago and we have no on-premise Exchange any longer. In the portal, I tried to set a primary SMTP address, and received this error:

The operation on mailbox "John Smith" failed because it's out of the current user's write scope. The action 'Set-Mailbox', 'EmailAddresses', can't be performed on the object 'John Smith' because the object is being synchronized from your on-premises organization. This action should be performed on the object in your on-premises organization.

Our DC's Windows Powershell doesn't support that command. I'd have been surprised if it did.

This is probably relevant- we performed the Sync by changing UPN's on user accounts. The sync works like a charm. But we need to be able to manage accounts.
0
Comment
Question by:jconklin-ansinc-net
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 42

Accepted Solution

by:
Vasil Michev (MVP) earned 500 total points
ID: 41725570
That's the whole idea of the sync - you transfer the source of authority to you on-prem AD and any changes in objects and their attributes should be done on-prem. That's also the reason why the only supported configuration is by having an Exchange server on-prem. If you dont have such server, you can still edit the attributes via ADUC/ADSI Edit/PowerShell, however you will be in unsupported scenario.

If you're only concerned about the primary SMTP address, there's a workaround. You can use the following cmdlet to change it directly in the cloud:

Set-Mailbox user@domain.com -WindowsEmailAddress new@domain.com

Open in new window


This cmdlet will add new@domain.com as the primary SMTP, while preserving user@domain.com as a secondary alias. It will work regardless of the object's sync status.
0
 

Author Closing Comment

by:jconklin-ansinc-net
ID: 41727583
The Powershell command worked. Thanks!
0

Featured Post

On Demand Webinar - Networking for the Cloud Era

This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article describes how to import an Outlook PST file to Office 365 using a third party product to avoid Microsoft's Azure command line tool, saving you time.
After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
This Experts Exchange video Micro Tutorial shows how to tell Microsoft Office that a word is NOT spelled correctly. Microsoft Office has a built-in, main dictionary that is shared by Office apps, including Excel, Outlook, PowerPoint, and Word. When …
Migrating to Microsoft Office 365 is becoming increasingly popular for organizations both large and small. If you have made the leap to Microsoft’s cloud platform, you know that you will need to create a corporate email signature for your Office 365…

626 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question