Merge pull request #212765 from SnehaGunda/SynapseIssues1

Testing TOC link

Author: prmerger-automator[bot]

articles/synapse-analytics/security/workspace-data-exfiltration-protection.md

@@ -5,7 +5,7 @@ author: WilliamDAssafMSFT
 ms.service: synapse-analytics 
 ms.topic: conceptual
 ms.subservice: security 
-ms.date: 12/01/2020 
+ms.date: 10/17/2022
 ms.author: wiassaf
 ms.reviewer: sngun
 ---
@@ -25,7 +25,7 @@ After the workspace is created with data exfiltration protection enabled, the ow
 ## Sample workspace with data exfiltration protection enabled
 Let us use an example to illustrate data exfiltration protection for Synapse workspaces. Contoso has Azure resources in Tenant A and Tenant B and there is a need for these resources to connect securely. A Synapse workspace has been created in Tenant A with Tenant B added as an approved Azure AD tenant. The diagram shows private endpoint connections to Azure Storage accounts in Tenant A and Tenant B that have been approved by the Storage account owners. The diagram also shows blocked private endpoint creation. The creation of this private endpoint was blocked as it targeted an Azure Storage account in the Fabrikam Azure AD tenant, which is not an approved Azure AD tenant for Contoso’s workspace.
 
-:::image type="content" source="media/workspace-data-exfiltration-protection/workspace-data-exfiltration-protection-diagram.png" alt-text="This diagram shows how data exfiltration protection is implemented for Synapse workspaces":::
+:::image type="content" source="media/workspace-data-exfiltration-protection/workspace-data-exfiltration-protection-diagram.png" alt-text="This diagram shows how data exfiltration protection is implemented for Synapse workspaces" lightbox="./media/workspace-data-exfiltration-protection/workspace-data-exfiltration-protection-diagram.png":::
 
 >[!IMPORTANT]
 >