Skip to content

Commit af529c0

Browse files
update screenshots and small edits
1 parent 263c30d commit af529c0

File tree

3 files changed

+11
-12
lines changed

3 files changed

+11
-12
lines changed
65.8 KB
Loading
39.8 KB
Loading

articles/sentinel/workspace-manager.md

Lines changed: 11 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -39,14 +39,13 @@ Depending on your scenario, consider these architectures:
3939
## Enable workspace manager on the central workspace
4040
Enable the central workspace once you have decided which Microsoft Sentinel workspace should be the workspace manager.
4141

42-
1. Navigate to the **Settings** blade in the parent workspace, and toggle "On" the workspace manager configuration setting.
43-
1. Once enabled, a new blade **Workspace manager (preview)** appears on the left menu under **Configuration**.
42+
1. Navigate to the **Settings** blade in the parent workspace, and toggle **On** the workspace manager configuration setting to "Make this workspace a parent".
43+
1. Once enabled, a new menu **Workspace manager (preview)** appears under **Configuration**.
4444

45-
Here's a comparison of the feature off and enabled side by side.
46-
:::image type="content" source="media/workspace-manager/enable-workspace-manager-enabled.png" alt-text="Screenshot shows the workspace manager configuration settings. The menu item added for workspace manager is highlighted and the toggle button on.":::
45+
:::image type="content" source="media/workspace-manager/enable-workspace-manager-on.png" alt-text="Screenshot shows the workspace manager configuration settings. The menu item added for workspace manager is highlighted and the toggle button on.":::
4746

4847
## Onboard member workspaces
49-
Member workspaces are the set of workspaces to be managed by workspace manager. You can onboard some or all of the workspaces in the tenant, and across multiple tenants as well (if Azure Lighthouse is enabled).
48+
Member workspaces are the set of workspaces to be managed by workspace manager. Onboard some or all of the workspaces in the tenant, and across multiple tenants as well (if Azure Lighthouse is enabled).
5049
1. Navigate to workspace manager and select "Add workspaces"
5150
:::image type="content" source="media/workspace-manager/add-workspace.png" alt-text="Screenshot shows the add workspace menu." lightbox="media/workspace-manager/add-workspace.png":::
5251
1. Select the member workspace(s) you would like to onboard to workspace manager.
@@ -70,23 +69,23 @@ Workspace manager groups allow you to organize workspaces together based on busi
7069
1. On the **Create or update group** page, enter a **Name** and **Description** for the group.
7170
:::image type="content" source="media/workspace-manager/add-group-name.png" alt-text="Screenshot shows the group create or update configuration page.":::
7271

73-
1. In the **Select workspaces** tab, click **Add** and select the member workspaces that you would like to add to the group.
72+
1. In the **Select workspaces** tab, select **Add** and select the member workspaces that you would like to add to the group.
7473
1. In the **Select content** tab, you have 2 ways to add content items.
7574
- Method 1: Select the **Add** menu and choose **All content**. This pulls all active content currently deployed in the central workspace. This list is a point-in-time snapshot that selects only active content, not templates.
7675
- Method 2: Select the **Add** menu and choose **Content**. This opens a **Select content** pane to custom select the content to be added.
7776
:::image type="content" source="media/workspace-manager/add-group-content.png" alt-text="Screenshot shows the group content selection.":::
7877

79-
1. After either method, you can further filter the content before you **Review + create**.
80-
1. Once successfully created, the **Group count** increases and your groups are reflected in the **Groups tab**.
78+
1. Filter the content as needed before you **Review + create**.
79+
1. Once created, the **Group count** increases and your groups are reflected in the **Groups tab**.
8180

8281
## Publish the Group definition
8382
At this point, the content items selected haven't been published to the member workspace(s) yet.
8483

85-
1. Select the group > Click the **Publish content** button.
84+
1. Select the group > **Publish content**.
8685

8786
:::image type="content" source="media/workspace-manager/publish-group.png" alt-text="Screenshot shows the group publish window.":::
8887

89-
To bulk publish, multi-select the desired groups and click on **Publish**.
88+
To bulk publish, multi-select the desired groups and select **Publish**.
9089
:::image type="content" source="media/workspace-manager/publish-groups.png" alt-text="Screenshot shows the multi-select group publishing window.":::
9190

9291
1. The **Last publish status** column updates to reflect **In progress**.
@@ -99,8 +98,8 @@ At this point, the content items selected haven't been published to the member w
9998

10099

101100
### Troubleshooting
102-
Each publish attempt has a link to help with troubleshooting if something goes wrong. Click the **Failed** hyperlink, to open the job failure details window. A status for each content item and target workspace pair is displayed.
103-
:::image type="content" source="media/workspace-manager/publish-groups-job-details.png" alt-text="Screenshot shows the job details of a group publishing failure event." lightbox="media/workspace-manager/publish-groups-job-details.png":::
101+
Each publish attempt has a link to help with troubleshooting if content items fail to publish. Even if just one fails, the publish status shows as **Failed**. Select the **Failed** hyperlink to open the job failure details window. A status for each content item and target workspace pair is displayed.
102+
:::image type="content" source="media/workspace-manager/publish-groups-job-details-failure.png" alt-text="Screenshot shows the job details of a group publishing failure event." lightbox="media/workspace-manager/publish-groups-job-details-failure.png":::
104103

105104
Common reasons for failure include:
106105
- Content items referenced in the group definition no longer exist at the time of publish (have been deleted).

0 commit comments

Comments
 (0)