With each new service pack released, the process for protecting mailbox content hosted in Microsoft o365 is further refined. The release of SP12 brings the following changes:
- Combined & simplified agent install. Rather than choosing “Mailbox” or “Database” etc the binaries are combined into a single “Exchange” client.
- If you need the OWA proxy enabler or Offline mining tool, these are available as separate installs.
- No need for the scheduled tasks to update the service account permissions on new mailboxes.
This post will focus on “Exchange Mailbox Agent User Mailbox Office 365 with Exchange Using Azure AD Environment” as detailed on the official documentation here.
There’s a few things to set up before you can start protecting the mailboxes. These are summarised below and detailed in the following sections.
- Server to install the Commvault Exchange agent
- Administration account for Office365
- Exchange Online Service account
- Must be an online mailbox
- Setup via admin.microsoft.com
- Local System Account
- Member of Local administrators on machine
- Index Server
- Job Results Directory
- Must be a UNC Path
- Mailbox Configuration Policies
- Storage Policy
Microsoft Tenant Configuration
- Connect to o365 with Powershell
$UserCredential = Get-Credential $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection Import-PSSession $Session
You’ll be prompted for a username and password, use the Administration account for Office365 mentioned in the prerequisites.
- Run the following commands:
get-ExecutionPolicy set-ExecutionPolicy RemoteSigned Enable-OrganizationCustomization
You may at this point see the following:
Not a problem, just continue to the next step.
- You now need to provide the service account (the one with the online mailbox mentioned earlier) with view only recipient permissions.
New-RoleGroup -Name "ExchangeonlinebackupGrp" -Roles "ApplicationImpersonation", "View-Only Recipients" -Members svcCommvault
- Register the o365 application with Exchange using AzureAD, do this via https://portal.azure.com:
- Goto Azure Active Directory (left hand side)
- Choose App Registrations
- Select New Application Registration
- Complete the fields as follows (feel free to use a different name)
- Click Create.
- Note down the Application ID (you’ll need this later to set up the pseudoclient)
- Click the Settings button once the app is created, Select the properties button on the right hand side.
- Scroll to the bottom and change Multi-tenanted to yes.
- Click Save
- Select Settings–>Keys
- You’re going to create a new key, complete the form as follows, adjust the first two fields as you see fit:
- Copy the Key value & description, you’ll need this later. May be worth remembering the expiry date too.
- Now select the Required Permissions menu. Click Add.
- Choose Select an API then Microsoft Graph
- Scroll down to Read Directory data, check the box and click Select.
- Click Done then Grant Permissions. Click Yes when prompted.
- On the left hand side, click Azure Active Directory then Properties. Note down the value in the Directory ID field.
Now it’s time to ensure you have the Exchange Policies, Index Server, Job Results Folder & Storage Policy setup. The latter 3 of these tasks are already well documented however the following should be noted:
- The Job results directory needs to be shared (i.e. \\UNC Path) visible to all mailbox backup proxies
The primary copy retentionRetention for the mailboxes is governed by the Retention Policy and not by the Storage Policy as is typical with other agents. For this reason it is worth having a separate storage policy for the mailbox backups.
- The mailbox agent index server should not be the MediaAgent responsible for you’re library and storage policies.
- The mailbox pseudoclient to index server is a 1:1 relationship. It is possible via a registry key to have multiple pseudoclients use the same index server, however; if the multiple pseudoclients have any crossover you will very likely experience data loss.
- Review the index store requirements before deploying the index server. If you’re doing this in a lab you can ususally start small and ramp up the specs on-the-fly.
- You must have a web server installed in your environment, typical Commcells have this installed on the CommServe however larger CommCells split this role out to a dedicated server.
This is a copy from my previous post but the information is still valid:
The four new policy types are as follows:
- Archiving – Archive is the new Backup. This policy dictates what messages will be protected, it has no effect on stubbing.
- Cleanup – If you are archiving, this is where it is configured.
- Retention – Primary Copy retention is configured here and will override any retention settings configured in the storage policy. Secondary copies will still adhere to the Storage Policy values.
- Journal – The new compliance archive. Use this for journal mailboxes.
Policies are configured under Policies, Configuration Policies, Exchange policies as shown below:
Only configure the policies you need, for a standard mailbox backup (no archive) setup, your policies listing may look like this:
Creating the Index Server
To create the logical Index Server (assuming you’ve installed the index store package) do the following:
- From the Commvault Console, right click Client Computers –> Index Servers and select New Index Server.
- Complete the fields on the General tab. If possible ensure the drive nominated for the Index Directory is formatted as 64kb block size. The Storage Policy, although optional; is used to backup the index.
- On the Roles tab, click Add, select Exchange Index, and move it to the Include field.
- On the Nodes tab; add the server on which you installed the Index Store package.
- Click OK. There will be a delay while the index is created, you may notice the following status on the bar at the bottom of the screen
Creating the Mailbox Client
You’ll need to have the Index server & policies ready before continuing to the mailbox client creation.
- Right click the CommServe name at the top of the CommCell Browser on the right hand side and select All Tasks –> Add/Remove Software –> New Client.
- Expand Exchange Mailbox and select User Mailbox.
- Complete the fields as shown below. Note: I have used the index server to host the job results directory which isn’t best practice, but OK for a lab.
- On the access nodes page, select a client (or clients) that has the Commvault Exchange package installed.
- On the Environment Type page, choose Exchange Online (Access Through Azure Active Directory).
- On the Azure App Details page enter the following:
- Application ID: as noted down earlier
- Key Value: As described (The auto generated key)
- Azure Directory ID: Noted down earlier
- On the service account settings page you’ll need to add 2 accounts:
- The Exchange online service account, this is the one we granted permission to earlier.
- A local system account. This needs to have local admin rights on your exchange proxy(ies).
- Optional: On the Recall Service, enter the URL for your web server as shown below. This is only used if Archiving or Content store viewer is implemented.
- Click Finish!
- To test that you are able to query the instance for its mailboxes navigate to MailboxAgent –> ExchangeMailbox –> User Mailbox and click the Mailbox Tab at the bottom of the screen.
- Right Click in the white space above the Tabs and choose New Association – User.
- On the Create New Association box, click Configure then Discover (Choose Yes at prompt).
- If your expected list of mailboxes appears, you’re doing it right!
The next step is to configure the auto associations. This can be easily achieved by following the official instructions here.