|
| 1 | +Retention labels help manage how long content is kept and what happens when that period ends. When content requires review before deletion, you can configure labels to trigger a disposition review. This ensures important items are reviewed by the right people before they're permanently deleted. |
| 2 | + |
| 3 | +In this exercise, you first create a role group that allows selected users to review items marked for disposition. Then you create a retention label for vendor contracts and configure it to start a disposition review after five years. You'll define a review stage, assign a reviewer, and publish the label so it's available in Microsoft 365. |
| 4 | + |
| 5 | +**Estimated time to complete**: 15-20 minutes |
| 6 | + |
| 7 | +> [!IMPORTANT] |
| 8 | +> To complete this exercise, you need access to Microsoft Purview features through one of these Microsoft 365 licenses: |
| 9 | +> |
| 10 | +> - A Microsoft 365 E3 license is required to create and publish retention labels. |
| 11 | +> - A Microsoft 365 E5 license, or the E5 Information Protection and Governance add-on, is required for disposition review. |
| 12 | +> |
| 13 | +> If your tenant doesn't include these features, some tasks in the exercise might not be available. You can still follow the steps to understand how the configuration works or skip any unsupported tasks. |
| 14 | +> |
| 15 | +> If you don't have access to these features, you can join the **[Microsoft 365 Developer Program](https://developer.microsoft.com/microsoft-365/dev-program)**. This program provides a free Microsoft 365 E5 developer subscription with access to many Purview capabilities. |
| 16 | +
|
| 17 | +## Create a role group for disposition reviewers |
| 18 | + |
| 19 | +Before assigning someone as a disposition reviewer, they must be in a role group with the necessary permissions. Use this task to create a role group and assign members who will review content marked for deletion. |
| 20 | + |
| 21 | +1. Navigate to [Microsoft Purview](https://purview.microsoft.com) and sign in. |
| 22 | +1. In the Microsoft Purview portal, go to **Settings** |
| 23 | +1. Expand **Roles and scopes**, then select **Role groups**. |
| 24 | +1. Select **Create role group**. |
| 25 | +1. On the **Name the role group** page, enter: |
| 26 | + |
| 27 | + - **Name**: `Disposition Reviewers` |
| 28 | + - **Description**: `Grants members permission to review and take action on content marked for disposition.` |
| 29 | + |
| 30 | +1. Select **Next**. |
| 31 | +1. On the **Add roles to the group** page, select **Choose roles**. |
| 32 | +1. On the **Choose roles** page, select **Disposition Management**, then select **Select** at the bottom of the page. |
| 33 | +1. Select **Next**. |
| 34 | +1. On the **Add members to the role group** page, select **Choose users** and add the users needed to conduct a disposition review, then select **Select** at the bottom of the page. |
| 35 | +1. Select **Next**. |
| 36 | +1. On the **Review the role group and finish** page, confirm your settings, then select **Create**. |
| 37 | +1. After your role group is created, select **Done**. |
| 38 | + |
| 39 | +The users you added to this role group can now be selected as reviewers when you configure a disposition stage in a retention label. This ensures they have permission to view and act on content pending deletion. |
| 40 | + |
| 41 | +## Create and publish a retention label with disposition review |
| 42 | + |
| 43 | +Use this task to configure a retention label that applies to vendor contracts. The label keeps content for five years, then starts a disposition review so a reviewer can decide whether to delete or retain the item. After you create the label, you’ll publish it so it's available across Microsoft 365. |
| 44 | + |
| 45 | +1. In the Microsoft Purview portal, go to **Solutions** > **Data Lifecycle Management**. |
| 46 | +1. Select **Retention labels**. |
| 47 | +1. Select **+ Create a label**. |
| 48 | +1. On the **Name your retention label** page, enter: |
| 49 | + |
| 50 | + - **Name**: `Vendor agreements - disposition review` |
| 51 | + - **Description for admins**: `Applies to vendor contracts. Retains for 5 years, then requires disposition review.` |
| 52 | + - **Description for users**: `Use for vendor contracts. Retention ends with review.` |
| 53 | + |
| 54 | +1. Select **Next**. |
| 55 | +1. On the **Define label settings** page, select **Retain items forever or for a specific period**, then select **Next**. |
| 56 | +1. On the **Define the retention period** page: |
| 57 | + |
| 58 | + - Set the retention period to **5 years**. |
| 59 | + - Start retention based on **when items were created**. |
| 60 | + |
| 61 | +1. Select **Next**. |
| 62 | +1. On the **Choose what happens after the retention period** page, select **Start a disposition review**, then select **Create stages and assign reviewers**. |
| 63 | +1. On the **Create stages and assign reviewers** page: |
| 64 | + |
| 65 | + - Enable **Automatic stage approval** |
| 66 | + - Set the automatic disposition approval to **14 days**. |
| 67 | + - Select **Add a stage** |
| 68 | + - Name the stage `Vendor agreement review`, then select **OK**. |
| 69 | + - Choose a user who is a member of the Disposition Reviewers role group you created earlier. |
| 70 | + - Select **OK** at the bottom of the reviewers page. |
| 71 | + |
| 72 | +1. Back on the **Choose what happens after the retention period** page, select **Next**. |
| 73 | +1. On the **Review and finish** page, confirm your settings, then select **Create label**. |
| 74 | +1. After your label is created, select **Publish this label to Microsoft 365 locations**, then select **Done**. |
| 75 | +1. On the **Choose labels to publish** page, make sure the **Vendor agreements - disposition review** label is selected, then select **Next**. |
| 76 | +1. On the **Policy Scope** page, leave the default selected, then select **Next**. |
| 77 | +1. On the **Choose the type of retention policy to create**, select **Static**. |
| 78 | +1. On the **Choose where to publish labels** page, select **All locations. Includes content from Exchange email, Office 365 groups, OneDrive and SharePoint documents.**, then select **Next**. |
| 79 | +1. On the **Name your policy** page, enter: |
| 80 | + |
| 81 | + - **Name**: `Vendor agreements disposition policy` |
| 82 | + - **Description**: `Apply to vendor contracts that need to be kept and reviewed later.` |
| 83 | + |
| 84 | +1. On the **Finish** page, confirm your settings, then select **Submit**. |
| 85 | +1. After your policy is created, select **Done**. |
| 86 | + |
| 87 | +This configuration helps ensure vendor contracts are reviewed before deletion. Disposition review gives your organization a chance to keep important content longer when needed, supporting more flexible retention decisions. |
| 88 | + |
| 89 | +## Check your work |
| 90 | + |
| 91 | +Review the role group, label, and policy you created to make sure they're configured as expected. |
| 92 | + |
| 93 | +1. Go to **Settings** > **Roles and scopes** > **Role groups**. |
| 94 | +1. Confirm that `Disposition Reviewers` is listed and includes: |
| 95 | + |
| 96 | + - The **Disposition Management** role |
| 97 | + - At least one assigned user |
| 98 | + |
| 99 | +1. Go to **Data Lifecycle Management** > **Retention labels**. |
| 100 | +1. Confirm that `Vendor agreements - disposition review` is listed. |
| 101 | +1. Open the label and check that: |
| 102 | + |
| 103 | + - The retention duration is set to 5 years |
| 104 | + - Retention starts when items are created |
| 105 | + - The action after the period is **Disposition review** |
| 106 | + - The review stage is named `Vendor agreement review` with automatic approval after 14 days |
| 107 | + |
| 108 | +1. Go to **Retention policies** and confirm that `Vendor agreements disposition policy` is listed. |
| 109 | +1. Open the policy and check that: |
| 110 | + |
| 111 | + - The correct label is included |
| 112 | + - The policy type is **Static** |
| 113 | + - All Microsoft 365 content locations are selected |
| 114 | + |
| 115 | +These steps help ensure that disposition review is properly configured. Verifying the label, policy, and reviewer permissions helps avoid gaps that could delay or block retention decisions. |
0 commit comments