Merge pull request #7967 from MicrosoftDocs/main

Taojunshen · web-flow · commit ffc1be853ada · 2025-04-18T06:02:35.000+08:00
4/17/2025 PM Publish
diff --git a/docs/architecture/gsa-deployment-guide-intro.md b/docs/architecture/gsa-deployment-guide-intro.md
@@ -19,7 +19,7 @@ Here are key Global Secure Access deployment scenarios:
 - Secure and monitor Microsoft Traffic for on-site and remote employees.
 - Secure and monitor internet traffic for on-site and remote employees.
 
-This Deployment Guide helps you to plan and deploy Microsoft Global Secure Access. See [Global Secure Access licensing overview](../global-secure-access/overview-what-is-global-secure-access.md#licensing-overview) for licensing information. While most of the services are generally available (GA), some parts of the service are in public preview. ​
+This Deployment Guide helps you to plan and deploy Microsoft Global Secure Access. See [Global Secure Access licensing overview](../global-secure-access/overview-what-is-global-secure-access.md#licensing-overview) for licensing information. While most of the services are generally available (GA), some parts of the service are in public preview. ​See [425 Show: Plan and Implement your Global Secure Access deployment](https://youtu.be/px6dd9ZJ7R0) for a video walk through detailing deployment planning and implementation recommendations.
 
 ## Perform a Proof of Concept
 
@@ -35,6 +35,8 @@ Depending on which capabilities you plan to deploy in a PoC for Microsoft Global
 - Deploy and test Microsoft Entra Private Access: One hour
 - Close PoC: 30 minutes
 
+See [425 Show: Global Secure Access Proof of Concept Deep Dive](https://youtu.be/BKLvA0p_v1g) for a video walk-through detailing proof of concept procedures.
+
 ## Initiate your Global Secure Access project
 
 Project initiation is the first step in any successful project. At the start of project initiation, you decided to implement Microsoft Global Secure Access. Project success depends on you to understand requirements, define success criteria, and ensure appropriate communications. Be sure to manage expectations, outcomes, and responsibilities.
@@ -274,12 +276,14 @@ Congratulations! You completed your Microsoft Global Secure Access deployment. T
 
 ## Next steps
 
+- [425 Show: Plan and Implement your Global Secure Access deployment](https://youtu.be/px6dd9ZJ7R0).
 - Learn how to accelerate your transition to a Zero Trust security model with [Microsoft Entra Suite and Microsoft's unified security operations platform](https://www.microsoft.com/security/blog/2024/07/11/simplified-zero-trust-security-with-the-microsoft-entra-suite-and-unified-security-operations-platform-now-generally-available/)
 - [Microsoft Global Secure Access deployment guide for Microsoft Traffic](gsa-deployment-guide-microsoft-traffic.md)
 - [Microsoft Global Secure Access Deployment Guide for Microsoft Entra Internet Access](gsa-deployment-guide-internet-access.md)
 - [Microsoft Global Secure Access Deployment Guide for Microsoft Entra Private Access](gsa-deployment-guide-private-access.md)
 - [Simulate remote network connectivity using Azure Virtual Network Gateway - Global Secure Access](../global-secure-access/how-to-simulate-remote-network.md)
 - [Simulate remote network connectivity using Azure vWAN - Global Secure Access](../global-secure-access/how-to-create-remote-network-vwan.md)
 - [Introduction to Global Secure Access Proof of Concept Guidance](gsa-poc-guidance-intro.md)
+- [Video - 425 Show: Global Secure Access Proof of Concept Deep Dive](https://youtu.be/BKLvA0p_v1g)
 - [Global Secure Access Proof of Concept Guidance - Configure Microsoft Entra Private Access](gsa-poc-private-access.md)
 - [Global Secure Access Proof of Concept Guidance - Configure Microsoft Entra Internet Access](gsa-poc-internet-access.md)
diff --git a/docs/global-secure-access/concept-edr-antivirus-coexistence.md b/docs/global-secure-access/concept-edr-antivirus-coexistence.md
@@ -0,0 +1,38 @@
+---
+title: EDR and antivirus coexistence with Global Secure Access client
+description: Learn about endpoint detection and response and antivirus solution coexistence with Global Secure Access client.
+author: jricketts
+manager: martinco
+ms.author: jricketts
+ms.service: global-secure-access
+ms.topic: concept-article
+ms.date: 03/28/2025
+
+#CustomerIntent: As an administrator, I want to configure endpoint detection and response and antivirus solution coexistence with Global Secure Access client so that I can improve system performance.
+---
+# Configure endpoint detection and response and antivirus solution coexistence with Global Secure Access client
+
+Running antivirus solutions such as Microsoft Defender for Endpoint side by side with the Global Secure Access client can affect system performance. If your system experiences [high CPU usage or performance issues](/defender-endpoint/troubleshoot-performance-issues), exclude Global Secure Access client processes from your antivirus solution.
+
+## Configuration overview
+
+In your antivirus solution, configure exclusions and bypasses for all Global Secure Access client processes:
+
+- `C:\Program Files\Global Secure Access Client\GlobalSecureAccessClientManagerService.exe`
+- `C:\Program Files\Global Secure Access Client\GlobalSecureAccessEngineService.exe`
+- `C:\Program Files\Global Secure Access Client\GlobalSecureAccessETLController.exe`
+- `C:\Program Files\Global Secure Access Client\GlobalSecureAccessTunnelingService.exe`
+- `C:\Program Files\Global Secure Access Client\TrayApp\\GlobalSecureAccessClient.exe`
+- `C:\Program Files\Global Secure Access Client\PolicyService\\GlobalSecureAccessPolicyRetrieverService.exe`
+- `C:\Program Files\Global Secure Access Client\LogsCollector\\LogsCollector.exe`
+- `C:\Program Files\Global Secure Access Client\AuthenticationRunner\\GlobalSecureAccessAuthenticationRunner.exe`
+- `C:\Program Files\Global Secure Access Client\AdvancedDiagnostics\\GlobalSecureAccessClientAdvancedDiagnostics.exe`
+
+To exclude these processes from Microsoft Defender for Endpoint, see [Configure custom exclusions for Microsoft Defender Antivirus](/defender-endpoint/configure-exclusions-microsoft-defender-antivirus).
+
+## Next steps
+
+-   Install the Windows client: [The Global Secure Access Client for Windows - Global Secure Access \| Microsoft Learn](how-to-install-windows-client.md)
+-   Install the macOS client: [The Global Secure Access Client for macOS - Global Secure Access \| Microsoft Learn](how-to-install-macos-client.md)
+-   Install the Android client: [The Global Secure Access Client for Android - Global Secure Access \| Microsoft Learn](how-to-install-android-client.md)
+-   Install the iOS client: [The Global Secure Access Client for iOS (Preview) - Global Secure Access \| Microsoft Learn](how-to-install-ios-client.md)
diff --git a/docs/global-secure-access/reference-current-known-limitations.md b/docs/global-secure-access/reference-current-known-limitations.md
@@ -225,7 +225,6 @@ Known limitations for remote networks include:
 
 ## Access controls limitations
 Known limitations for access controls include:   
-- Continuous access evaluation (CAE) isn't currently supported for Universal Conditional Access for Microsoft traffic.
 - Applying Conditional Access policies to Private Access traffic isn't currently supported. To model this behavior, you can apply a Conditional Access policy at the application level for Quick Access and Global Secure Access apps. For more information, see [Apply Conditional Access to Private Access apps](how-to-target-resource-private-access-apps.md).
 - Microsoft traffic can be accessed through remote network connectivity without the Global Secure Access Client; however the Conditional Access policy isn't enforced. In other words, Conditional Access policies for the Global Secure Access Microsoft traffic are only enforced when a user has the Global Secure Access Client.
 - Compliant network check data plane enforcement (preview) with Continuous Access Evaluation is supported for SharePoint Online and Exchange Online.
diff --git a/docs/global-secure-access/toc.yml b/docs/global-secure-access/toc.yml
@@ -61,6 +61,8 @@ items:
         href: how-to-install-android-client.md
       - name: Install the iOS client
         href: how-to-install-ios-client.md
+      - name: EDR/antivirus coexistence with Global Secure Access client
+        href: concept-edr-antivirus-coexistence.md
   - name: Remote networks
     expanded: false
     items:
diff --git a/docs/workload-id/workload-identity-federation-config-app-trust-managed-identity.md b/docs/workload-id/workload-identity-federation-config-app-trust-managed-identity.md
@@ -1,5 +1,5 @@
 ---
-title: Configure an application to trust a managed identity (preview)
+title: Configure an application to trust a managed identity
 description: Learn how to configure an application to trust a managed identity in Microsoft Entra ID.
 author: cilwerner
 manager: CelesteDG
@@ -11,7 +11,7 @@ ms.reviewer: hosamsh
 #Customer intent: As an application developer, I want to configure my application to trust a managed identity so that I can access Microsoft Entra protected resources without needing to use or manage application secrets or certificates.
 ---
 
-# Configure an application to trust a managed identity (preview)
+# Configure an application to trust a managed identity
 
 This article describes how to configure a Microsoft Entra application to trust a managed identity. You can then exchange the managed identity token for an access token that can access Microsoft Entra protected resources without needing to use or manage App secrets.
 
