SPARK utilizes Azure Automation Accounts. By default, five automation accounts are established within the tenant. The first automation account, aa-spark-autoamation0 acts as the primary. All additional automation accounts are secondary and used only for batch and parallel processing time intensive operations.
Requirements
The Azure Administrator will be required for this step. The user must have:
- Owner role for the subscription
Step 1 - Create Azure Runbooks
This section will utilize scripts to create the Azure runbooks. Complete the following steps to run the script.
- Download the scripts from the table below and place them in the same folder
| Scripts |
|---|
| ProvisionAzureAutomationAccounts |
| rb-spark-manage-crawl-state |
| rb-spark-manage-dl-notifications |
| rb-spark-sendemail-toDL |
| rb-spark-sitecollector |
| rb-spark-siteinventory-mgmt |
2. Reference the variables spreadsheet and update the ProvisionAzureAutomationAccounts.ps1 script variables found in the Variable section
3. Open PowerShell v7.2+
4. Run the script and validate the runbooks are created
[!WARNING] Create Runbook Error: “Conflict”
When running this automation script, you may run into an error:
New-AzAutomationAccount: Operation returned an invalid status code ‘Conflict’
This is based on the limitation of exceeding the quota for Automation accounts in your subscription in the region.
Step 2 - Set Identity
For aa-spark-automation0, complete the following steps:
- Select Identity under the Account Settings section of the left navigation
- Under the System assigned tab, turn the Status to On
- Save the change
Step 3 - Configure aa-spark-automation0 SAMI App Role Assignment
This script configures the aa-spark-automation0 SAMI automation account App Role Assignment of Exchange.ManageAsApp.
- Reference the Assign_SAMI_aa_spark_automation0_ExchangeManageAsApp
- Uncomment the appropriate connection string based on your tenant
- Run the script