Microsoft Entra Global Secure Access
GeneralInstall Macos Client
In brief
The documentation now warns that, starting with version 1.1.26060207, including the already-installed com.microsoft.autoupdate2 application in Intune detection rules might cause a conflict.
What Entra admins need to know
Administrators deploying the app should review their Intune detection rules and may remove com.microsoft.autoupdate2 to avoid a conflict.
This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.
Documentation change
View on Microsoft LearnThe comparison below shows only the changed extract. Use the full-page view for complete context.
To deploy the Global Secure Access client's .pkg file through Microsoft Intune as a managed app:
- Download the
GlobalSecureAccessClient.pkgfile from the Microsoft Entra admin center.
@@ -51,7 +51,7 @@ The client uses system extensions and a transparent application proxy that you n To deploy the Global Secure Access client's .pkg file through Microsoft Intune as a managed app: > [!IMPORTANT]-> Beginning with version **1.1.26060207**, the app package includes the `com.microsoft.autoupdate2` application to support future use cases. You can optionally remove `com.microsoft.autoupdate2` from the Intune detection rules when deploying the app.+> Beginning with version **1.1.26060207**, the app package includes the `com.microsoft.autoupdate2` application to support future use cases. If `com.microsoft.autoupdate2` is already installed, including it in the Intune detection rules might cause a conflict. You can optionally remove `com.microsoft.autoupdate2` from the detection rules when deploying the app. 1. Download the `GlobalSecureAccessClient.pkg` file from the Microsoft Entra admin center.