One item that needs to be addressed is how to enable a remote archive in a Hybrid Exchange solution. Is there really a write scope restriction in RBAC that is blocking the command? Required fields are marked *. Thanks for your feedback, it helps us improve the site. You can follow the question or vote as helpful, but you cannot reply to this thread. Created a new test user and found that the archive works fine for test user. We can see Archive but when try to open it, we get. Ensure that your legal team is heavily involved in this process. On the Archive Settings page, the default of no archive is then change to provision the archive mailbox directly in Exchange Online. It is also possible to directly create the archive mailbox in Office 365 when the mailbox is initially created. Finally we complete the wizard which then starts execution. Since it is referring about scope do not get confused with RBAC, all we need to do is to enable archiving from Exchange On-premise and then do force dirsync. If so, there is no method to directly move the online archive mailbox (Office 365) to the on-premises mailbox. Office 365 mailbox with archive also in Office 365 . This lab was created using Exchange 2010 SP3 so it does not have the old school service domain present. The Office 365 tenant was successfully added to the Exchange 2010 Management Console. Office 365 Error – Cannot Start Microsoft Outlook–Quick Check, Automating Enable-Remote Mailbox – 250 Hello, Enable-RemoteMailbox–Is It A Chicken Or Egg – 250 Hello, Unable to Remove Exchange 2010 Public Folder Database. To enable using Exchange 2013 EAC: Open the EAC ->Click "Recipients" -> Mailboxes Select the mailbox for which archiving to be enabled Click Enable under In-Place Archive -> Yes. To view both cloud mailboxes and on-premises mailboxes ensure that the focus is placed upon the Recipient Configuration node. Since we are not very clear the more detailed information about your current environment, please run above commands on the test user that is working well, so we can comparing between them. Currently we are using exchange 2013/16 servers and I have enabled online archive for the on-premise user. The same happens with remote PowerShell to Exchange Online. This is highlighted in the image below. You can also use a PowerShell command in the Exchange management shell, which is even easier: Clicking the browse button allows you to easily see the target delivery domain that was configured. Sorry for not responding in time.