Office 365 Beta: Provisioning of Archive in the Cloud from On-premises Exchange 2010 Server

In Exchange 2010, Microsoft introduced "Personal Archives," a feature intended to allow you to reduce or eliminate PST files by provisioning archive mailboxes for your users.With Office 365 beta, Microsoft also enabled organizations to store archive mailboxes in the cloud, while maintaining the primary mailbox on your on-premises Mailbox servers running Exchange 2010 SP1. Users […]

In Exchange 2010, Microsoft introduced "Personal Archives," a feature intended to allow you to reduce or eliminate PST files by provisioning archive mailboxes for your users.

With Office 365 beta, Microsoft also enabled organizations to store archive mailboxes in the cloud, while maintaining the primary mailbox on your on-premises Mailbox servers running Exchange 2010 SP1. Users can seamlessly access their primary on-premises mailbox and their archive in the cloud using Outlook 2010 /2007 and Outlook Web App.

Here's a workaround to manually update the archive provisioning status in the on-premises organization using the ChangeArchiveStatus.ps1 script.

Note: It's a temporary workaround required for the Office 365 beta -- it'll not be required for Office 365 GA.

  1. Provision an archive mailbox in the cloud using EMC or the Shell on-premises
  2. Wait for DirSync cyle to complete (this may take up to 2 hours)
  3. Confirm that archive has been provisioned in Office 365. This step requires your organization's Office 365 account credentials.
    1. Use Shell to connect to Office 365. For details, see Connect Windows PowerShell to Outlook Live.
    2. Run Get-Mailbox <user> | fl ArchiveStatus and check if the value of the ArchiveStatus property is set to active.

    Important: Do not perform the following steps until the archive status in Office 365 changes to active.

  4. Using a Shell session to an on-premises Exchange server, run the ChangeArchiveStatus.ps1 script using the following syntax:

    ChangeArchiveStatus.ps1 <user> $true

  5. Refresh the EMC and verify that the user's archive status is now active.

[Source]