Expiring Today—Celebrate National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

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

Posted on 2016-07-22
2
Medium Priority
?
549 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 43

Accepted Solution

by:
Vasil Michev (MVP) earned 2000 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

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

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

This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
Check out this step-by-step guide for using the newly updated Experts Exchange mobile app—released on May 30.
Access reports are powerful and flexible. Learn how to create a query and then a grouped report using the wizard. Modify the report design after the wizard is done to make it look better. There will be another video to explain how to put the final p…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…

719 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