Merge pull request #116 from riswinto/master

update note style

Author: riswinto

Instructions/Labs/Lab1_Ex2_sensitive_information_types.md

@@ -97,11 +97,7 @@ You've received reports that some documents containing employee IDs aren't being
 
 1. Search for `Contoso Employee IDs` in the list and select the SIT name to open the details page.
 
-    > **Note: Refresh the list of sensitive info types**
-    >
-    > If you're unable to find the Contoso Employee IDs on the sensitive info type page, try refreshing the list of sensitive info types from the top menu.
-    >
-    > ![Screenshot showing the Sensitive info types page with the Refresh button highlighted.](../Media/refresh-sensitive-info-type.png)
+    > **Note: Refresh the list of sensitive info types**<p>If you're unable to find the Contoso Employee IDs on the sensitive info type page, try refreshing the list of sensitive info types from the top menu.<p>![Screenshot showing the Sensitive info types page with the Refresh button highlighted.](../Media/refresh-sensitive-info-type.png)
 
 1. Select **Edit** at the top of the flyout to modify the SIT.
 
@@ -304,9 +300,7 @@ In this task, you'll hash and upload the actual data for the EDM-based classific
 
     You should get a message that the command completed successfully.
 
-    > **Note: EDM group membership propagation**
-    >
-    > If the last command fails, it possibly takes more time until the **EDM_DataUploaders** group membership is applied. It can take up to one hour until it is possible to download the schema file. If it fails, proceed to the next task and return to this step later.
+    > **Note: EDM group membership propagation**<p>If the last command fails, it possibly takes more time until the **EDM_DataUploaders** group membership is applied. It can take up to one hour until it is possible to download the schema file. If it fails, proceed to the next task and return to this step later.
 
 1. Hash the database file and upload it to the EDM-based classification sensitive information type by running the following script in PowerShell:
 
@@ -326,9 +320,7 @@ In this task, you'll hash and upload the actual data for the EDM-based classific
 
     Alternatively, you can also refresh the **EDM classifiers** window in the Microsoft Purview portal to check the status of the hash. Once the status is set to **Index complete** the hash is complete.
 
-    > **Note: EDM hash processing time**
-    >
-    > This process might take some time. You might need to run the GetSession script or refresh the EDM classifiers page several times before the status indicates that the hash is complete.
+    > **Note: EDM hash processing time**<p>This process might take some time. You might need to run the GetSession script or refresh the EDM classifiers page several times before the status indicates that the hash is complete.
 
     ![Screenshot showing the EDM hash status set to Completed in PowerShell.](../Media/edm-hash-completed.png)
 

Instructions/Labs/Lab1_Ex3_sensitivity_labels.md

@@ -60,7 +60,7 @@ With sensitivity label support enabled, you'll confirm that the tenant uses the
 
 1. In the **Confirm migration to modern label scheme** dialog box, select **Confirm migration**.
 
-    > **Note: Migration processing time**<br>The migration process might take a few minutes to complete.
+    > **Note: Migration processing time**<p>The migration process might take a few minutes to complete.
 
 You've successfully migrated your tenant to the modern sensitivity label scheme. New labels and policies you create will now use the modern configuration experience.
 

Instructions/Labs/Lab4_Ex1_insider_risk_management.md

@@ -175,9 +175,7 @@ You've successfully enabled Defender for Endpoint to share alerts with Microsoft
 
 In this task, you'll enable advanced indicators and create a priority user group that can be used in targeted insider risk policies.
 
-> **Note: Defender for Endpoint indicator availability**
->
-> Microsoft Defender for Endpoint indicators might appear greyed out and unselectable if the integration from the previous task hasn't finished processing. If that happens, wait a few minutes and refresh the page before continuing.
+> **Note: Defender for Endpoint indicator availability**<p>Microsoft Defender for Endpoint indicators might appear greyed out and unselectable if the integration from the previous task hasn't finished processing. If that happens, wait a few minutes and refresh the page before continuing.
 
 1. In **Microsoft Edge**, navigate to `https://purview.microsoft.com`.
 

Instructions/Labs/Lab4_Ex2_adaptive_protection.md

@@ -12,9 +12,7 @@ lab:
 
 # Lab 4 - Exercise 2 - Implement Adaptive Protection
 
-> **Warning: Temporary skip - Adaptive Protection is currently unavailable on lab tenants.**
->
-> This exercise depends on Adaptive Protection functionality that is not working in the current tenant environment. Skip this exercise until further notice. The rest of the lab set is unaffected.
+> **Warning: Temporary skip - Adaptive Protection is currently unavailable on lab tenants.**<p>This exercise depends on Adaptive Protection functionality that is not working in the current tenant environment. Skip this exercise until further notice. The rest of the lab set is unaffected.
 
 You are Joni Sherman, the Information Security Administrator for Contoso Ltd. Your role involves protecting sensitive data and responding to insider risks. To enhance protection, you'll enable Microsoft Purview Adaptive Protection, which dynamically adjusts data loss prevention (DLP) enforcement based on insider risk levels.
 
@@ -80,11 +78,7 @@ To add another layer of enforcement, you can use insider risk levels to restrict
 
 1. Navigate **Microsoft Entra admin center** at `https://entra.microsoft.com`, and sign in as **MOD Administrator**, `admin@WWLxZZZZZZ.onmicrosoft.com` (where ZZZZZZ is your unique tenant prefix provided by your lab hosting provider). Admin's password should be provided by your lab hosting provider.
 
-    > **Note: Multi-factor authentication prompt**
-    >
-    > If you're prompted for MFA while signing in, open the **Microsoft Authenticator** app on your mobile device and approve the sign-in request.
-    >
-    > After approval, you'll be redirected to the **Microsoft Entra admin center**.
+    > **Note: Multi-factor authentication prompt**<p>If you're prompted for MFA while signing in, open the **Microsoft Authenticator** app on your mobile device and approve the sign-in request. After approval, you'll be redirected to the **Microsoft Entra admin center**.
 
 1. In the Microsoft Entra admin center, navigate to **Protection** > **Conditional Access** > **Policies**.
 

Instructions/Labs/Lab5_Ex1_audit.md

@@ -82,9 +82,7 @@ In this task, you'll export the DLP audit search results for offline analysis or
 
 1. When the export completes, select the **Download file** link in the green **Your export is complete** banner.
 
-> **Note: Audit export file format**
->
-> Audit export files are saved in CSV format and can be opened in any text editor or spreadsheet application. For easier review, use Excel or another spreadsheet tool. In this lab environment, you can open the CSV in Notepad to confirm that the export completed successfully.
+> **Note: Audit export file format**<p>Audit export files are saved in CSV format and can be opened in any text editor or spreadsheet application. For easier review, use Excel or another spreadsheet tool. In this lab environment, you can open the CSV in Notepad to confirm that the export completed successfully.
 
 You've exported DLP-related audit logs, which can be used for offline review or recordkeeping.
 

Instructions/Labs/Lab6_Ex1_dspm_for_ai.md

@@ -49,9 +49,7 @@ Contoso is preparing for broader AI adoption, and the security team needs a unif
 
 1. Select **Start setup**.
 
-> **Note: DSPM setup actions**
->
-> Selecting **Start setup** enables any required analytics that aren't already enabled and starts the initial DSPM scan.
+> **Note: DSPM setup actions**<p>Selecting **Start setup** enables any required analytics that aren't already enabled and starts the initial DSPM scan.
 
 You've enabled DSPM analytics and started the initial scan that correlates sensitive-data risks across Microsoft Purview.
 
@@ -98,8 +96,6 @@ Contoso is preparing for broader Copilot and AI adoption, and wants to find cont
 
 1. Back on the **Data risk assessments** page, select **Unlabeled SharePoint Content Assessment** to review its status and scope.
 
-> **Note: Assessment scan processing time**
->
-> The assessment scan can take time to complete. Review the assessment results after processing finishes to identify files that need labeling, access review, or other remediation.
+> **Note: Assessment scan processing time**<p>The assessment scan can take time to complete. Review the assessment results after processing finishes to identify files that need labeling, access review, or other remediation.
 
 You've created a DSPM data risk assessment that will identify potential oversharing risks in unlabeled SharePoint content. Use the results with the DSPM posture and objectives pages to prioritize appropriate labeling, DLP, and access-remediation actions.

Instructions/Labs/Lab7_Ex1_validation.md

@@ -51,9 +51,7 @@ In this task, you'll verify that published sensitivity labels are available to u
 
     ![Screenshot showing the sensitivity label button in Word.](../Media/word_label.png)
 
-    > **Note: Label propagation delay**
-    >
-    > It can take 24-48 hours for newly published sensitivity labels to be available for application. If the newly created sensitivity labels aren't available, you can use **Confidential** > **All Employees** for this exercise.
+    > **Note: Label propagation delay**<p>It can take 24-48 hours for newly published sensitivity labels to be available for application. If the newly created sensitivity labels aren't available, you can use **Confidential** > **All Employees** for this exercise.
 
 1. Change the sensitivity label to **Highly Confidential** > **Project - Falcon** to verify the business justification dialog appears.