Merge pull request #167626 from batamig/best-practices-architecture

removing internal text and updating non blocking PR review issues

Author: PRMerger10

articles/sentinel/automate-responses-with-playbooks.md

@@ -241,7 +241,7 @@ Manual triggering is available from the Azure Sentinel portal in the following b
 
 ### Run a playbook manually on an incident
 
-Not supported yet. <!--make this a note instead? -->
+Not supported yet.
 
 ## Manage your playbooks
 

articles/sentinel/best-practices-workspace-architecture.md

@@ -27,14 +27,6 @@ While fewer workspaces are simpler to manage, you may have specific needs for mu
 
 When determining how many tenants and workspaces to use, consider that most Azure Sentinel features operate by using a single workspace or Azure Sentinel instance, and Azure Sentinel ingests all logs housed within the workspace.
 
-<!--
-Therefore, for example, if you have both security-related and non-security logs, or logs that should not be ingested by Azure Sentinel, you may want to create an additional workspace to store the non-Azure Sentinel logs and avoid unwanted costs.
-
-The following image shows an architecture where security and non-security logs go to separate workspaces, with Azure Sentinel ingesting only the security-related logs.
-
-:::image type="content" source="media/best-practices/separate-workspaces-for-different-logs.png" alt-text="Separate workspaces for security-related logs and non-security logs.":::
--->
-
 > [!IMPORTANT]
 > Costs are one of the main considerations when determining Azure Sentinel architecture. For more information, see [Azure Sentinel costs and billing](azure-sentinel-billing.md).
 >
@@ -112,7 +104,7 @@ For more information, see [Permissions in Azure Sentinel](roles.md).
 The following image shows a simplified version of a workspace architecture where security and operations teams need access to different sets of data, and resource-context RBAC is used to provide the required permissions.
 
 
-[ ![Sample architecture for resource-context RBAC.](media/resource-context-rbac/resource-context-rbac-sample.png) ](media/resource-context-rbac/resource-context-rbac-sample.png#lightbox)
+[ ![Diagram of a sample architecture for resource-context RBAC.](media/resource-context-rbac/resource-context-rbac-sample.png) ](media/resource-context-rbac/resource-context-rbac-sample.png#lightbox)
 
 In this image, the Azure Sentinel workspace is placed in a separate subscription to better isolate permissions.
 

articles/sentinel/sample-workspace-designs.md

@@ -28,7 +28,7 @@ The Contoso Corporation is a multinational business with headquarters in London.
 
 Due to an acquisition several years ago, Contoso has two Azure AD tenants: `contoso.onmicrosoft.com` and `wingtip.onmicrosoft.com`. Each tenant has its own Office 365 instance and multiple Azure subscriptions, as shown in the following image:
 
-:::image type="content" source="media/best-practices/contoso-tenants.png" alt-text="Contoso tenants, each with separate sets of subscriptions.":::
+:::image type="content" source="media/best-practices/contoso-tenants.png" alt-text="Diagram of Contoso tenants, each with separate sets of subscriptions." border="false":::
 
 ### Contoso compliance and regional deployment
 
@@ -83,7 +83,7 @@ The following steps apply the [Azure Sentinel workspace design decision tree](de
 
 The resulting Azure Sentinel workspace design for Contoso is illustrated in the following image:
 
-:::image type="content" source="media/best-practices/contoso-solution.png" alt-text="Contoso's solution, with a separate workspace for the Ops team.":::
+:::image type="content" source="media/best-practices/contoso-solution.png" alt-text="Diagram of Contoso's solution, with a separate workspace for the Ops team." border="false":::
 
 The suggested solution includes:
 
@@ -165,7 +165,7 @@ The following steps apply the [Azure Sentinel workspace design decision tree](de
 
 The resulting Azure Sentinel workspace design for Fabrikam is illustrated in the following image, including only key log sources for the sake of design simplicity:
 
-:::image type="content" source="media/best-practices/fabrikam-solution.png" alt-text="Fabrikam's solution, with a separate workspace for the Ops team.":::
+:::image type="content" source="media/best-practices/fabrikam-solution.png" alt-text="Diagram of Fabrikam's solution, with a separate workspace for the Ops team." border="false" :::
 
 The suggested solution includes:
 
@@ -238,7 +238,7 @@ The following steps apply the [Azure Sentinel workspace design decision tree](de
 
 The resulting Azure Sentinel workspace design for Adventure Works is illustrated in the following image, including only key log sources for the sake of design simplicity:
 
-:::image type="content" source="media/best-practices/adventure-works-solution.png" alt-text="Adventure Works's solution, with a separate workspaces for each Azure AD tenant.":::
+:::image type="content" source="media/best-practices/adventure-works-solution.png" alt-text="Diagram of Adventure Works's solution, with a separate workspaces for each Azure AD tenant." border="false":::
 
 The suggested solution includes: