|Category||Microsoft Docs article||Related commit history on GitHub||Change details|
|compliance||Compliance Manager Mcca||https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/compliance-manager-mcca.md||
After you install MCCA, you can run MCCA and generate a report. To run a report:```powershell Get-MCCAReport ```
+ If you are U.S. Government GCC High or U.S. Government DoD customer, you will have to provide an additional input parameter to run the report.
+ Get-MCCAReport -ExchangeEnvironmentName O365USGovGCCHigh
+ Get-MCCAReport -ExchangeEnvironmentName O365USGovDoD
+ ```+ 3. Once MCCA runs, it does an initial version check and ask for credentials. At the Input the user name prompt, sign in with your Microsoft 365 account email address ([view the roles eligible to create reports](#role-based-reporting)). Then enter your password at the password prompt. Your report will then take approximately 2-5 minutes to generate. When itΓÇÖs done, a browser window opens and displays your HTML report. Every time you run the tool, it will ask for your credentials and generate a new report. This report is stored locally in the following directory:
|compliance||Export View Audit Log Records||https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/compliance/export-view-audit-log-records.md||
The next step is to use the JSON transform feature in the Power Query Editor in> [!NOTE] > The JSON properties displayed in the previous screenshot (after you click **Load more**) are based on the properties found in the **AuditData** column from the first 1,000 rows in the CSV file. If there are different JSON properties in records after the first 1,000 rows, these properties (and a corresponding column) won't be included when the **AuditData** column is split into multiple columns. To help prevent this, consider re-running the audit log search and narrow the search criteria so that fewer records are returned. Another workaround is to filter items in the **Operations** column to reduce the number of rows (before you perform step 5 above) before transforming the JSON object in the **AuditData** column.
+ > [!TIP]
+ > To view an attribute within a list such as AuditData.AffectedItems, click the **Expand** icon in the upper right corner of the column you want to pull an attribute from, and then select **Expand to New Row**. From there it will be a record and you can click the **Expand** icon in the upper right corner of the column, view the attributes, and select the one you want to view or extract.+ 8. Do one of the following things to format the title of the columns that are added for each JSON property that's selected. - Unselect the **Use original column name as prefix** checkbox to use the name of the JSON property as the column names; for example, **RecordType** or **SourceFileName**.
|enterprise||Cross Tenant Mailbox Migration||https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/cross-tenant-mailbox-migration.md||
Prepare the source tenant:| Parameter | Value | Required or Optional ||--|--|
- | -TargetTenantDomain | Target tenant domain, such as contoso\.onmicrosoft.com. | Required |
- | -ResourceTenantDomain | Source tenant domain, such as fabrikam\.onmicrosoft.com. | Required |
+ | -TargetTenantDomain | Target tenant domain, such as fabrikam\.onmicrosoft.com. | Required |
+ | -ResourceTenantDomain | Source tenant domain, such as contoso\.onmicrosoft.com. | Required || -ResourceTenantAdminEmail | Source tenant adminΓÇÖs email address. This is the source tenant admin who will be consenting to the use of the mailbox migration application sent from the target admin. This is the admin who will receive the email invite for the application. | Required | | -ResourceTenantId | Source tenant organization ID (GUID). | Required | | -SubscriptionId | The Azure subscription to use for creating resources. | Required |
The target admin setup is now complete!| Parameter | Value | |--|| | -SourceMailboxMovePublishedScopes | Mail-enabled security group created by source tenant for the identities/mailboxes that are in scope for migration. |
- | -ResourceTenantDomain | Source tenant domain name, such as fabrikam\.onmicrosoft.com. |
+ | -ResourceTenantDomain | Source tenant domain name, such as contoso\.onmicrosoft.com. || -ApplicationId | Azure application ID (GUID) of the application used for migration. Application ID available via your Azure portal (Azure AD, Enterprise Applications, app name, application ID) or included in your invitation email. |
- | -TargetTenantDomain | Target tenant domain name, such as contoso\.onmicrosoft.com. |
+ | -TargetTenantDomain | Target tenant domain name, such as fabrikam\.onmicrosoft.com. || -TargetTenantId | Tenant ID of the target tenant. For example, the Azure AD tenant ID of contoso\.onmicrosoft.com tenant. | |||