You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: learn-pr/wwl-sci/security-copilot-exercises/includes/2-first-run-experience.md
+11-13Lines changed: 11 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,10 +3,8 @@ The organization you work for wants to increase the efficiency and capabilities
3
3
In this exercise, you go through the first run experience of Security Copilot to provision Copilot with one security compute unit (SCU).
4
4
5
5
> [!NOTE]
6
-
>The environment for this exercise is a simulation generated from the product. As a limited simulation, links on a page may not be enabled and text-based inputs that fall outside of the specified script may not be supported. A pop-up message will display stating, "This feature is not available within the simulation." When this occurs, select OK and continue the exercise steps.
7
-
>:::image type="content" source="../media/simulation-pop-up-error.png" alt-text="Screenshot of pop-up screen indicating that this feature is not available within the simulation.":::
8
-
>
9
-
> Also, Microsoft Security Copilot was previously referred to as Microsoft Copilot for Security. Throughout this simulation, you'll find that the user interface still reflects the original name.
6
+
>The environment for this exercise is a simulation generated from the product. As a limited simulation, links on a page may not be enabled and text-based inputs that fall outside of the specified script may not be supported. A pop-up message displays stating, "This feature is not available within the simulation." When this occurs, select OK and continue the exercise steps.
7
+
>:::image type="content" source="../media/simulation-pop-up-error.png" alt-text="Screenshot of pop-up screen indicating that this feature isn't available within the simulation.":::
10
8
11
9
### Exercise
12
10
@@ -15,7 +13,7 @@ For this exercise, you're logged in as Avery Howard and you have the global admi
15
13
This exercise should take approximately **15** minutes to complete.
16
14
17
15
> [!NOTE]
18
-
> When a lab instruction calls for opening a link to the simulated environment, it is generally recommended that you open the link in a new browser window so that you can simultaneously view the instructions and the exercise environment. To do so, select the right mouse key and select the option.
16
+
> When a lab instruction calls for opening a link to the simulated environment, it's recommended that you open the link in a new browser window so that you can simultaneously view the instructions and the exercise environment. To do so, select the right mouse key and select the option.
19
17
20
18
#### Task: Set role permissions
21
19
@@ -28,11 +26,11 @@ In this task, you walk through the process of ensuring you have the appropriate
28
26
29
27
Why is this needed? As a Global Administrator in Microsoft Entra ID, you might not have access to all subscriptions and management groups in your directory. Microsoft Entra ID and Azure resources are secured independently from one another. That is, Microsoft Entra role assignments don't grant access to Azure resources, and Azure role assignments don't grant access to Microsoft Entra ID. When you elevate your access, you're assigned the User Access Administrator role in Azure at root scope (/). This allows you to view all resources and assign access in any subscription or management group in the directory. For details, see [Elevate access to manage all Azure subscriptions and management groups.](/azure/role-based-access-control/elevate-access-global-admin).
30
28
31
-
Once you're assigned the User Access Administrator role in Azure, you can assign a user the necessary access to provision SCUs for Copilot. For the purpose of this exercise only, which is to show you the steps involved, you'll be assigning yourself the necessary access. The steps that follow will guide you through the process.
29
+
Once you're assigned the User Access Administrator role in Azure, you can assign a user the necessary access to provision SCUs for Copilot. In this exercise only, which is to show you the steps involved, you are assigning yourself the necessary access. The steps that follow guide you through the process.
32
30
33
31
1. Open the simulated environment by selecting this link: **[Azure portal](https://app.highlights.guide/start/6d7270b9-7187-456a-ac16-97bc227d5c27?token=045faae1-1078-4eac-bf56-e12472eddaf9&link=1&azure-portal=true)**.
34
32
35
-
1. You'll start by enabling Access management for Azure resources. To access this setting:
33
+
1. You start by enabling Access management for Azure resources. To access this setting:
36
34
1. From the Azure portal, select **Microsoft Entra ID**.
37
35
1. From the left navigation panel, expand **Manage**.
38
36
1. From the left navigation panel, scroll down and select **Properties**.
@@ -54,7 +52,7 @@ As an owner to the Azure subscription, you'll now be able to provision capacity
54
52
55
53
#### Task: First run experience
56
54
57
-
When you first open Security Copilot, a wizard guides you through the steps in setting up capacity for your organization and some and initial configuration of settings.
55
+
When you first open Security Copilot, a wizard guides you through the steps in setting up capacity for your organization and some and initial configuration of settings.
58
56
59
57
In order to start using Security Copilot, you must provision the capacity, which is defined in terms of security compute units. There are two options for provisioning capacity:
60
58
@@ -65,8 +63,8 @@ For this exercise, you provision capacity through Security Copilot. When you fir
65
63
66
64
1. Open the simulated environment by selecting this link: **[Microsoft Security Copilot](https://app.highlights.guide/start/6d7270b9-7187-456a-ac16-97bc227d5c27?token=045faae1-1078-4eac-bf56-e12472eddaf9&azure-portal=true)**.
67
65
68
-
1.Follow the steps in the Wizard, select **Get started**.
69
-
1. On this page, you set up your security capacity. For any of the fields listed below, you can select the information icon for more information.
66
+
1.The first page you see in the wizard is to set up your security capacity.
67
+
1. For any of the fields listed, you can select the information icon for more information.
70
68
1. Azure subscription: From the drop-down, select **Woodgrove - GTP Demos (External/Sponsored)**.
71
69
1. Resource group: From the drop-down, select **RG-1**. Alternatively, you can select **Create a new resource group** and enter resource group name.
72
70
1. Capacity name: The default capacity name is prepopulated. Leave the default capacity name.
@@ -77,14 +75,14 @@ For this exercise, you provision capacity through Security Copilot. When you fir
77
75
1. Use overage units when needed: You can enable the option for overage units. If the setting is enabled, you can select the option for no limit or set a max-limit by selecting the number of overage units per hour.
78
76
1. Select the box, **"I acknowledge that I have read, understood, and agree to the Terms and Conditions**.
79
77
1. Select **Continue** on the bottom right corner of the page.
80
-
1.You can select options to help improve Copilot. You can select the toggle based on your preferences. Select **Continue**.
81
-
1.As part of the initial setup, information about Copilot's access and storage of Microsoft 365 data is displayed. Review the information. Although there's no setting to configure on this page, it provides guidance on where you can configure the option to share your Microsoft 365 service data Copilot and the implication of not sharing our Microsoft 365 dates with Copilot. Select **Continue**. You'll see this option in the subsequent task, after you complete the first run experience.
78
+
1.Help improve Copilot: You can select the toggle based on your preferences. Select **Continue**.
79
+
1. Copilot's access and storage of Microsoft 365 service data: Although there's no setting to configure on this page, it provides guidance on where you can configure the option to share your Microsoft 365 service data Copilot and the implication of not sharing our Microsoft 365 dates with Copilot. Select **Continue**.
82
80
1. Logging audit data in Microsoft Purview: The audit logging feature in Security Copilot uses Microsoft Purview to process and store admin actions, user actions, and Copilot responses. This includes data from any Microsoft and non-Microsoft integrations. You can choose to disable this option. It's important to note that this option is applied to any workspace that is created. Select **Continue**.
83
81
1. Copilot access: As part of the initial setup, Copilot gives you the option to add the **Recommended Microsoft Security roles** to the contributor group. If you choose to not add it during the setup, you can add them later. The owners group includes the Global administrator and Security administrator role as Copilot owners, by default. In your production environment, you can change who has access to Copilot, once you've completed the initial setup. Select **Continue**.
84
82
1. You're all set! Select **Finish**.
85
83
1. Leave the browser tab open for the next task.
86
84
87
-
Task 2: Review owner settings
85
+
#### Task 2: Review owner settings
88
86
89
87
In the previous task, you provisioned capacity and some initial settings. Now that you completed the first run experience, you'll do some brief navigation within Copilot to view where some of those settings are found and can be updated. More detailed exploration of the Security Copilot standalone experience is covered in a subsequent unit.
Copy file name to clipboardExpand all lines: learn-pr/wwl-sci/security-copilot-exercises/includes/3-explore-standalone-experience.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,8 +7,7 @@ In this exercise, you explore all the key landmarks in the landing page of the s
7
7
> [!NOTE]
8
8
> The environment for this exercise is a simulation generated from the product. As a limited simulation, links on a page may not be enabled and text-based inputs that fall outside of the specified script may not be supported. A pop-up message displays stating, "This feature isn't available within the simulation." When this occurs, select OK and continue the exercise steps.
9
9
>:::image type="content" source="../media/simulation-pop-up-error.png" alt-text="Screenshot of pop-up screen indicating that this feature is not available within the simulation.":::
10
-
>
11
-
> Also, Microsoft Security Copilot was previously referred to as Microsoft Copilot for Security. Throughout this simulation, you'll find that the user interface still reflects the original name.
Copy file name to clipboardExpand all lines: learn-pr/wwl-sci/security-copilot-exercises/includes/3a-explore-workspaces.md
+11-21Lines changed: 11 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,23 +3,22 @@ A workspace is a scoped, tenant-bound environment where users, automations, and
3
3
As a security administrator for your organization, you have permission to create and manage workspaces in Copilot. In this exercise, you walk through tasks associated with creating and managing a workspace.
4
4
5
5
> [!NOTE]
6
-
> The environment for this exercise is a simulation generated from the product. As a limited simulation, links on a page may not be enabled and text-based inputs that fall outside of the specified script may not be supported. A pop-up message displays stating, "This feature isn't available within the simulation." When this occurs, select OK and continue the exercise steps.
7
-
>:::image type="content" source="../media/simulation-pop-up-error.png" alt-text="Screenshot of pop-up screen indicating that this feature is not available within the simulation.":::
8
-
>
9
-
> Also, Microsoft Security Copilot was previously referred to as Microsoft Copilot for Security. Throughout this simulation, you'll find that the user interface still reflects the original name.
6
+
> The environment for this exercise is a simulation generated from the product. As a limited simulation, links on a page may not be enabled and text-based inputs that fall outside of the specified script may not be supported. A pop-up message displays stating, "This feature is not available within the simulation." When this occurs, select OK and continue the exercise steps.
7
+
>:::image type="content" source="../media/simulation-pop-up-error.png" alt-text="Screenshot of pop-up screen indicating that this feature isn't available within the simulation.":::
8
+
10
9
11
10
### Exercise
12
11
13
-
For this exercise, you're logged in as Avery Howard and have the Security administrator role, which is one of the available roles that grants permission to create and manage workspaces.
12
+
For this exercise, you're logged in as Avery Howard and have the Security administrator role, which is one of the available roles that grants permission to create and manage workspaces. In this exercise, you start by viewing the settings available in the currently selected workspace, then you create a new workspace. Lastly, you work in the newly created workspace. By comparing the settings in the initially available workspace with the settings of the newly created workspace, you see first-hand how all user interactions happen within the context of a workspace.
14
13
15
14
This exercise should take approximately **15** minutes to complete.
16
15
17
16
> [!NOTE]
18
-
> When a lab instruction calls for opening a link to the simulated environment, it's generally recommended that you open the link in a new browser window so that you can simultaneously view the instructions and the exercise environment. To do so, select the right mouse key and select the option.
17
+
> When a lab instruction calls for opening a link to the simulated environment, it's recommended that you open the link in a new browser window so that you can simultaneously view the instructions and the exercise environment. To do so, select the right mouse key and select the option.
19
18
20
19
#### Task: View your interactions for the current workspace
21
20
22
-
In this task, you view some of your user interactions in the selected workspace, SecurityCopilot_Workspace. The settings and interactions that you set in this workspace will serve as a point of comparison against the new workspace that you'll create in the subsequent task.
21
+
In this task, you view some of your user interactions in the selected workspace, SecurityCopilot_Workspace. The settings and interactions that you set in this workspace serve as a point of comparison against the new workspace that you create in the subsequent task.
23
22
24
23
1. Open the simulated environment by selecting this link: **[Microsoft Security Copilot](https://app.highlights.guide/start/fa057153-57cc-486f-820b-109a96c15009?token=045faae1-1078-4eac-bf56-e12472eddaf9&azure-portal=true)**.
25
24
@@ -29,7 +28,7 @@ In this task, you view some of your user interactions in the selected workspace,
29
28
1. Select **Usage monitoring**.
30
29
1. Select **Owner settings**.
31
30
1. Any changes you make to configurable items in the owner settings apply to the given workspace, except for the setting for Logging audit data in Microsoft Purview.
32
-
1. Review the description under the setting, "Logging audit data in Microsoft Purview." The description states that this setting applies to all workspaces in your organization. If you change the setting, that change will apply for all workspaces.
31
+
1. Review the description under the setting, "Logging audit data in Microsoft Purview." The description states that this setting applies to all workspaces in your organization. If you change the setting, that change applies for all workspaces.
33
32
1. Select **Plugin settings**, then switch the toggle button to on, to manage plugin availability and restrict access. When you do this, all plugins are listed and set to Owners only.
34
33
1. Select **Role assignments**, and select **+Add recommended roles**. The Contributor role now reflects this option.
35
34
1. Select Microsoft Security Copilot from the breadcrumb to return to the main landing page
@@ -38,12 +37,12 @@ In this task, you view some of your user interactions in the selected workspace,
38
37
39
38
#### Task: Create a new workspace
40
39
41
-
In this task, you create a new workspace and assign it an available capacity. In this exercise, the capacity that will be assigned to the workspace has already been created.
40
+
In this task, you create a new workspace and assign it an available capacity. In this exercise, the capacity that is assigned to the workspace has already been created.
42
41
43
42
1. Select the **Menu** icon, select **Manage workspaces**. Note the banner shown. This banner indicates that there's a capacity that has been created and is not assigned to a workspace.
44
43
1. Select **+ New workspace**
45
44
1. Workspace name
46
-
1. Select the information icon. Note that once a pick a workspace name, you won't be able to change it.
45
+
1. Select the information icon. Once a pick a workspace name, you won't be able to change it.
47
46
1. Enter a name for your workspace, **Test-workspace**.
48
47
1. Capacity: When you create a workspace, you can assign an available capacity or create a new capacity.
49
48
1. First try to select a capacity that is in-use to view the experience. From the drop-down list, select **SecurtyCopilot_WorkspaceCapacity**. Note the message that appears. Select **Cancel** (in this simulation, you won't be able to disconnect and switch capacities).
@@ -63,7 +62,7 @@ In this task, you'll select and manage the workspace you created. You'll also be
63
62
1. From the drop-down list, select the workspace you created **Test-workspace**.
64
63
1. Select the **Menu** icon.
65
64
1. Select **My sessions**. As expected there are no sessions listed. The sessions that were listed for the SecurityCopilot_Workspace live only in that workspace.
66
-
1. Select **Usage monitoring**. The dashboard will show usage for this workspace only. As expected, there is no usage to show.
65
+
1. Select **Usage monitoring**. The dashboard shows usage for this workspace only. As expected, there's no usage to show.
67
66
1. Select **Owner settings**. The setting for Logging audit data in Microsoft Purview will be consistent for both workspaces. Other settings may be different based on what was selected in each workspace.
68
67
1. Select **Plugin settings**. Recall that in the SecurityCopilot_Workspace, setting to manage plugin availability and restrict access was enabled. In this new workspace, that setting isn't enabled.
69
68
1. Select **Role assignments**. The Contributor role doesn't include any members. In the first task, you explicitly added the recommended roles.
@@ -72,16 +71,7 @@ In this task, you'll select and manage the workspace you created. You'll also be
72
71
1. Select the **Menu** icon.
73
72
1. Select **My sessions**. Your session is displayed. As previously mentioned, all user interaction happens within the context of a workspace.
74
73
1. Select **Usage monitoring**. Your usage is displayed.
75
-
1. Keep this browser tab open, as you'll use it in the next task.
76
-
77
-
#### Task: Delete a workspace
78
-
79
-
In this task, you'll delete the workspace you created.
80
-
81
-
1. Select the **Menu** icon.
82
-
1. Select **Manage workspaces**.
83
-
1. Place your mouse cursor over the table entry for the newly created workspace. Note the two icons that appear. Select the **Delete** icon (the trash can).
84
-
1. Close the browser tab.
74
+
1. This concludes the task and the exercise, you can close the browser tab.
0 commit comments