AvePoint Docs
Graph API
My support tickets
Graph API
My support tickets
English

    Home > Aviator > Aviator for Microsoft 365 Groups > Create an Aviator Policy for Microsoft 365 Groups

    Export to PDF

    Create an Aviator Policy for Microsoft 365 Groups

    Aviator - Microsoft 365 Groups policies include the Group policy and Planner policy, which allow you to define the data filter and other settings in the Group or Planner level. For each level, Fly provides a system default policy for you. You can directly use the system default policy, or refer to the following steps to create a Group policy based on your needs.

    Create a Group Policy

    Refer to the following steps to create a Group policy:

    1. Click Settings in the left pane, and click Policies > Aviator policies > Microsoft 365 Groups.

    2. Under the Group policy tab, click Create Aviator policy. The Create Aviator policy panel appears.

    3. Enter a name and an optional description for the policy, and then click Next.

    4. In the Filter & conflict resolution step, complete the following settings:

      • Group – Select Planner and/or Membership if you want to copy or merge the planner data and/or Group members. With the Membership option selected, you can continue selecting to copy or merge guest users.

      • SharePoint team site – Define the object scopes of source team sites to be copied or merged.

        • All data in SharePoint team site – Select this checkbox to migrate all data of source team sites.

        • Only the default Documents library – Select this check to only migrate the default Documents libraries in team sites of Teams and private channels.

      • Group mailbox – Select the Mailbox checkbox to copy or merge the mailbox items of source Group mailboxes.

      • Conflict resolution – Configure the following conflict resolutions when the source object conflicts with an existing one in the destination during the Merge process.

        • SharePoint team site files – Refer to the following detailed information on each conflict resolution for files of source team sites.
    ResolutionConflictNo Conflict
    SkipIgnore the conflicting file and do nothing in the destination.A new file will be created.
    OverwriteDelete the conflicting file in the destination first and overwrite it with the source content.A new file will be created.
    Overwrite by last modified timeThe conflicting file with the latest modified time will be preserved in the destination.A new file will be created.
    AppendThe conflicting file will not be deleted. The destination conflicting file will be renamed as filename_bak. The migrated file will be renamed as filename_site name_trimmedfileID.A new file will be created.
    - **Mailbox item** – Refer to the following detailed information on each conflict resolution for source mailbox items.
    ResolutionConflictNo Conflict
    SkipIgnore the conflicting item and do nothing in the destination.A new item will be created.
    OverwriteDelete the conflicting item in the destination first and overwrite it with the source item.A new item will be created.

    1. Click Next to continue.

    2. In the Additional options & mappings step, define how to manage the sensitivity labels, IRM restrictions, and configure user mappings for the Aviator job.

      • To manage the sensitivity labels of files/emails during the migration, select an option below:

        *Note: If the source does not have the Microsoft Information Protection (MIP) service implemented or source files/emails do not have any sensitivity labels applied, select the first option for your migration to ensure a successful job.

        • No label insource, or migratefiles/emails with source label to destination (if file/email has label encryption, it will be inaccessible in the destination) – Select this option if there is no sensitivity label applied on source files/emails, or you want to keep the source sensitivity labels of the files/emails to the destination.

          After the migration, the migrated files/emails that have label encryption may not be accessed in the destination.

        • If a label exists, remove it during the migration (source label remains, it is removed from the file/email in the destination) – Select this option if you want to remove the source sensitivity labels from the files/emails.

          After the migration, the migrated files/emails do not have any sensitivity labels and can be accessed in the destination.

        • Apply same label in the destination (same label must exist in the destination) – This option removes the source sensitivity labels from the migrated files/emails during the migration, and applies existing destination sensitivity labels with the same display name to the migrated files/emails in the destination. The source sensitivity labels applied to source files/emails will not be removed from the source tenant.

        • Apply labels in the destination based on label mappings (labels must exist in both source and destination) – With this option, you can configure sensitivity label mappings to replace the source sensitivity labels applied to the migrated files/emails with existing destination sensitivity labels.

          According to the label mappings, Fly will remove the source sensitivity labels from the migrated files/emails during the migration, and apply the destination sensitivity labels to the migrated files/emails in the destination. The source sensitivity labels applied to source files/emails will not be removed from the source tenant.

          Click the Add (Button: Add button) button to Create Sensitivity Label Mappings to map the source and destination labels based on their display names. You can also select a previously created label mapping from the drop-down list to use it (Clicking View details can view and edit the detailed information of the selected label mapping.).

      • To manage the sensitivity labels of Groups during the migration, select an option below:

        *Note: If the source does not have the Microsoft Information Protection (MIP) service implemented or source Groups do not have any sensitivity labels configured in the Sensitivity setting, select the first option for your migration to ensure a successful job.

        • No label in source, or do not copy source label on Group to destination– Select this option to not keep the source sensitivity labels to the destination Groups.

        • Apply same label in the destination (identical label must exist in the destination) – Select this option to not keep the source sensitivity labels, and apply existing destination sensitivity labels of the same display name to the destination Groups.

        • Apply labels in the destination based on label mappings (labels must exist in both source and destination) – Select this option if you want to configure sensitivity label mappings to map the source sensitivity labels to existing destination labels based on their display names. You can click the Add (Button: Add button) button to Create Sensitivity Label Mappings to map the source and destination labels based on their display names.

          If the source Groups are applied with the source labels configured in the mapping, the Sensitivity setting value of their destination sites will be updated to the mapped destination labels.

      • Information rights management – Select the Remove source IRM restrictions from files checkbox if you want to remove the source IRM restrictions during the migration. If you deselect this checkbox, the source IRM restrictions will be kept to the destination, and the migrated files may be inaccessible in the destination.

      • User mapping – With the user mapping, you can map a source user to a destination one. You can also map a domain in the source to a destination domain. Users, securities, and user-related metadata can be migrated based on user mappings. Click Add (Button: Add button.) button to the right of the field to create a new one. Refer to the Create User Mappings section to view how to create a user mapping.

        You can also select a previously created user mapping from the drop-down list and click View details to view the detailed information of the selected user mapping. You can enter the keyword of a user mapping in the Search user mapping text box and press Enter on the keyboard to search the user mapping.

        *Note: For the users that have not been configured in user mappings, you can choose to map the users based on User principal name prefix, Display name, and/or Email address prefix. (Email address prefix is only supported for users of team sites.) Refer to the table below for property examples:

    PropertyUser Principal NameUser Principal Name PrefixDisplay NameEmail AddressEmail Address Prefix
    Property ExampleJohnSimon@onmicrosoft.comJohnSimon@JohnSimonJohnSimon@onmicrosoft.comJohnSimon@
    - Switch on/off the button of each property to configure whether you want to map users based on that property. - Click the Up or Down button of a property to configure the sequence for mapping users. > ***Note**: If all properties are disabled, user mappings are required.

    3. Click Save to save the policy. After creating the policy, you can click Set as default to set the policy as the default policy.

    On the Aviator policies page, you can manage existing policies.

    - Set as default – Select a policy and click **Set as default** to set it as the default policy. The default policy will be automatically selected when you create an Aviator job. - Edit Aviator policy – Click the policy name link to edit the policy. - > ***Note**: The system default policy cannot be edited. - Delete – Select one or multiple policies and click **Delete** to delete them. - > ***Note**: The system default policy cannot be deleted. - Copy – This allows you to quickly create a new policy with similar configurations by completing the following steps: 1. Select your target policy, and click **Make a copy**. You can also open your target policy, and click **Make a copy** on the **Edit migration policy** page. 2. Check the settings and make updates if necessary on the **Copy migration policy** page. 3. Click **Save**.

    Create a Planner Policy

    Refer to the following steps to create a Planner policy:

    1. Click Settings in the left pane, and click Policies > Aviator policies > Microsoft 365 Groups.

    2. Click the Planner policy tab.

    3. Click Create Aviator policy. The Create Aviator policy panel appears.

    4. Enter a name and an optional description for the policy, and then click Next.

    5. In the Filter & conflict resolution step, complete the following settings:

      • Plan – Select the objects of source plans to be copied or merged.

      • Membership – Select whether to migrate attachment permissions or add task assignees to destination team/group membership.

      • Conflict resolution – Specify the conflict resolution when the source content conflicts with an existing one in the destination during the Merge process.

    ResolutionConflictNo Conflict
    SkipIgnore the conflicting content and do nothing in the destination.A new content will be created.
    OverwriteDelete the conflicting content in the destination first and overwrite it with the source content.A new content will be created.
    Overwrite by last modified timeThe conflicting content with the latest modified time will be preserved in the destination.A new content will be created.

    1. Click Next to continue.

    2. In the Additional options & mappings step, define how to manage the sensitivity labels, IRM restrictions, and configure user mappings for the Aviator job.

      • To manage the sensitivity labels of files during the migration, select an option below:

        *Note: If the source does not have the Microsoft Information Protection (MIP) service implemented or source files do not have any sensitivity labels applied, select the first option for your migration to ensure a successful job.

        • No label insource, or migratefiles with source label to destination (if file has label encryption, it will be inaccessible in the destination) – Select this option if there is no sensitivity label applied on source files, or you want to keep the source sensitivity labels of the files to the destination.

          After the migration, the migrated files that have label encryption may not be accessed in the destination.

        • If a label exists, remove it during the migration (source label remains, it is removed from the file in the destination) – Select this option if you want to remove the source sensitivity labels from the files.

          After the migration, the migrated files do not have any sensitivity labels and can be accessed in the destination.

        • Apply same label in the destination (same label must exist in the destination) – This option removes the source sensitivity labels from the migrated files during the migration, and applies existing destination sensitivity labels with the same display name to the migrated files in the destination. The source sensitivity labels applied to source files will not be removed from the source tenant.

        • Apply labels in the destination based on label mappings (labels must exist in both source and destination) – With this option, you can configure sensitivity label mappings to replace the source sensitivity labels applied to the migrated files with existing destination sensitivity labels.

          According to the label mappings, Fly will remove the source sensitivity labels from the migrated files during the migration, and apply the destination sensitivity labels to the migrated files in the destination. The source sensitivity labels applied to source files will not be removed from the source tenant.

          Click the Add (Button: Add button) button to Create Sensitivity Label Mappings to map the source and destination labels based on their display names. You can also select a previously created label mapping from the drop-down list to use it (Clicking View details can view and edit the detailed information of the selected label mapping.).

      • Information rights management – Select the Remove source IRM restrictions from files checkbox if you want to remove the source IRM restrictions during the migration. If you deselect this checkbox, the source IRM restrictions will be kept to the destination, and the migrated files may be inaccessible in the destination.

      • User mapping – With a user mapping, you can map a source user to a destination one. You can also map a domain in the source to a destination domain. Users, securities, and user-related metadata can be migrated based on user mappings. Click Add (Button: Add button.) button to the right of the field to create a new one. Refer to the Create User Mappings section to view how to create a user mapping.

        You can also select a previously created user mapping from the drop-down list and click View details to view the detailed information of the selected user mapping. You can enter the keyword of a user mapping in the Search user mapping text box and press Enter on the keyboard to search the user mapping.

        *Note: For the users that have not been configured in user mappings, you can choose to map the users based on User principal name prefix, Display name, and/or Email address prefix. (Email address prefix is only supported for users of team sites.) Refer to the table below for property examples:

    PropertyUser Principal NameUser Principal Name PrefixDisplay NameEmail AddressEmail Address Prefix
    Property ExampleJohnSimon@onmicrosoft.comJohnSimon@JohnSimonJohnSimon@onmicrosoft.comJohnSimon@
    - Switch on/off the button of each property to configure whether you want to map users based on that property. - Click the Up or Down button of a property to configure the sequence for mapping users. > ***Note**: If all properties are disabled, user mappings are required.

    8. Click Save to save the policy. After creating the policy, you can click Set as default to set the policy as the default policy.

    On the Aviator policies page, you can manage existing policies.

    - Set as default – Select a policy and click **Set as default** to set it as the default policy. The default policy will be automatically selected when you create an Aviator job. - Edit – Click the policy name link to edit the policy. - > ***Note**: The system default policy cannot be edited. - Delete – Select one or multiple policies and click **Delete** to delete them. - > ***Note**: The system default policy cannot be deleted. - Copy – This allows you to quickly create a new policy with similar configurations by completing the following steps: 1. Open your target policy, and click **Make a copy** on the **Edit migration policy** page. 2. Check the settings and make updates if necessary on the **Copy migration policy** page. 3. Click **Save**.