Muokkaa

Jaa

Global Secure Access client for macOS (Preview)

  • Artikkeli

Important

The Global Secure Access client for macOS is currently in PREVIEW. This information relates to a prerelease product that may be substantially modified before it's released. Microsoft makes no warranties, expressed or implied, with respect to the information provided here.

The Global Secure Access client, an essential component of Global Secure Access, helps organizations manage and secure network traffic on end-user devices. The client's main role is to route traffic that needs to be secured by Global Secure Access to the cloud service. All other traffic goes directly to the network. The Forwarding Profiles, configured in the portal, determine which traffic the Global Secure Access client routes to the cloud service.

This article describes how to download and install the Global Secure Access client for macOS.

Prerequisites

  • A Mac device with an Intel, M1, M2, M3, or M4 processor, running macOS version 13 or newer.
  • A device registered to Microsoft Entra tenant using Company Portal.
  • A Microsoft Entra tenant onboarded to Global Secure Access.
  • Deployment of the Microsoft Enterprise single sign-on (SSO) plug-in for Apple devices is recommended for SSO experience based on the user who is signed in to the company portal.
  • An internet connection.

Download the client

The most current version of the Global Secure Access client is available to download from the Microsoft Entra admin center.

  1. Sign in to the Microsoft Entra admin center as a Global Secure Access Administrator.
  2. Browse to Global Secure Access > Connect > Client download.
  3. Select Download Client. Screenshot of the Client download screen with the Download Client button highlighted.

Install the Global Secure Access client

Automated installation

Use the following command for silent installation. Substitute your file path according to the download location of the .pkg file.

sudo installer -pkg ~/Downloads/GlobalSecureAccessClient.pkg -target / -verboseR

The client uses system extensions and a transparent application proxy that need to be approved during the installation. For a silent deployment without prompting the end user to allow these components, you can deploy a policy to automatically approve the components.

Allow system extensions through mobile device management (MDM)

The following instructions are for Microsoft Intune and you can adapt them for different MDMs:

  1. In the Microsoft Intune admin center, select Devices > Manage devices > Configuration > Policies > Create > New policy.
  2. Create a profile for the macOS platform based on a template of type Extensions. Select Create. Screenshot of the Create a profile form with the macOS Platform, Templates Profile type, and the Extensions template highlighted.
  3. On the Basics tab, enter a name for the new profile and select Next.
  4. On the Configuration settings tab, enter the Bundle identifier and the Team identifier of the two extensions according to the following table. Select Next.
Bundle identifier Team identifier
com.microsoft.naas.globalsecure.tunnel-df UBF8T346G9
com.microsoft.naas.globalsecure-df UBF8T346G9
  1. Complete the creation of the profile by assigning users and devices according to your needs.

Allow transparent application proxy through MDM

The following instructions are for Microsoft Intune and you can adapt them for different MDMs:

  1. In the Microsoft Intune admin center, select Devices > Manage devices > Configuration > Policies > Create > New policy.
  2. Create a profile for the macOS platform based on a template of type Custom and select Create. Screenshot of the Create a profile form with the macOS Platform, Templates Profile type, and Custom template highlighted.
  3. On the Basics tab, enter a Name for the profile. image.png
  4. On the Configuration settings tab, enter a Custom configuration profile name.
  5. Keep Deployment channel set to "Device channel."
  6. Upload an .xml file that contains the following data:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>PayloadDescription</key>
    <string>Ttransparent proxy settings</string>
    <key>PayloadDisplayName</key>
    <string>Global Secure Access Client - AppProxy</string>
    <key>PayloadIdentifier</key>
    <string>com.microsoft.naas.globalsecure-df.</string>
    <key>PayloadType</key>
    <string>Configuration</string>
    <key>PayloadUUID</key>
    <string>68C6A9A4-ECF8-4FB7-BA00-291610F998D6</string>
    <key>PayloadVersion</key>
    <real>1</real>
    <key>TransparentProxy</key>
    <dict>
        <key>AuthName</key>
        <string>NA</string>
        <key>AuthPassword</key>
        <string>NA</string>
        <key>AuthenticationMethod</key>
        <string>Password</string>
        <key>ProviderBundleIdentifier</key>
        <string>com.microsoft.naas.globalsecure.tunnel-df</string>
        <key>RemoteAddress</key>
        <string>100.64.0.0</string>
        <key>ProviderDesignatedRequirement</key>
        <string>identifier &quot;com.microsoft.naas.globalsecure.tunnel-df&quot; and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = UBF8T346G9</string>
        <key>Order</key>
        <string>1</string>
    </dict>
    <key>UserDefinedName</key>
    <string>Global Secure Access Client - AppProxy</string>
    <key>VPNSubType</key>
    <string>com.microsoft.naas.globalsecure.tunnel-df</string>
    <key>VPNType</key>
    <string>TransparentProxy</string>
</dict>
</plist>

Screenshot of the Configuration settings tab showing a portion of the .xml data.

  1. Complete the creation of the profile by assigning users and devices according to your needs.

Manual interactive installation

To manually install the Global Secure Access client:

  1. Run the GlobalSecureAccessClient.pkg setup file. The Install wizard launches. Follow the prompts.

  2. On the Introduction step, select Continue.

  3. On the License step, select Continue and then select Agree to accept the license agreement. Screenshot of the Install wizard on the SumLicense step, showing the software license agreement pop-up.

  4. On the Installation step, select Install.

  5. On the Summary step, when the installation is complete, select Close.

  6. Allow the Global Secure Access system extension.

    1. In the System Extension Blocked dialog, select Open System Settings.
      Screenshot of the System Extension Blocked dialog box with the Open System Settings highlighted.

    2. Allow the Global Secure Access client system extension by selecting Allow. Screenshot of the System Settings, open to the Privacy & Security options, showing a blocked application message, with the Allow button highlighted.

    3. In the Privacy & Security dialog, enter your username and password to validate the approval of the system extension. Then select Modify Settings.
      Screenshot of the Privacy & Security pop-up requesting sign-in credentials and the Modify Settings button highlighted.

    4. Complete the process by selecting Allow to enable the Global Secure Access client to add proxy configurations.
      Screenshot of the Global Secure Access client would like to add proxy configurations pop-up with the Allow button highlighted.

  7. After the installation is complete, you might be prompted to sign in to Microsoft Entra.

Note

If the Microsoft Enterprise SSO plug-in for Apple devices is deployed, the default behavior is to use single sign-on with the credentials entered in the company portal.

  1. The Global Secure Access - Connected icon appears in the system tray, indicating a successful connection to Global Secure Access.
    Screenshot of the system tray with the Global Secure Access - Connected icon highlighted.

Upgrade the Global Secure Access client

The client installer supports upgrades. You can use the installation wizard to install a new version on a device that is currently running a previous client version.

For a silent upgrade, use the following command.
Substitute your file path according to the download location of the .pkg file.

sudo installer -pkg ~/Downloads/GlobalSecureAccessClient.pkg -target / -verboseR

Uninstall the Global Secure Access client

To manually uninstall the Global Secure Access client, use the following command.

sudo /Applications/Global\ Secure\ Access\ Client.app/Contents/Resources/install_scripts/uninstall

If you're using an MDM, uninstall the client with the MDM.

Client actions

To view the available client menu actions, right-click the Global Secure Access system tray icon.
Screenshot showing the list of Global Secure Access client actions.

Action Description
Disable Disables the client until the user enables it again. When the user disables the client, they're prompted to enter a business justification and reenter their sign-in credentials. The business justification is logged.
Enable Enables the client.
Pause Pauses the client for either 10 minutes, until the user resumes the client, or until the device is restarted. When the user pauses the client, they're prompted to enter a business justification and reenter their sign-in credentials. The business justification is logged.
Resume Resumes the paused client.
Restart Restarts the client.
Collect logs Collects client logs and archives them in a zip file to share with Microsoft Support for investigation.
Settings Opens the Settings and Advanced diagnostics tool.
About Shows information regarding the product's version.

Client statuses in system tray icon

Icon Message Description
Global Secure Access Client The client is initializing and checking its connection to Global Secure Access.
Global Secure Access Client - Connected The client is connected to Global Secure Access.
Global Secure Access Client - Disabled The client is disabled because services are offline or the user disabled the client.
Global Secure Access Client - Disconnected The client failed to connect to Global Secure Access.
Global Secure Access Client - Some channels are unreachable The client is partially connected to Global Secure Access (that is, the connection to at least one channel failed: Microsoft Entra, Microsoft 365, Private Access, Internet Access).
Global Secure Access Client - Disabled by your organization Your organization disabled the client (that is, all traffic forwarding profiles are disabled).
Global Secure Access - Private Access is disabled The user disabled Private Access on this device.
Global Secure Access - could not connect to the Internet The client couldn't detect an internet connection. The device is either connected to a network that doesn't have an Internet connection or a network that requires captive portal sign in.

Settings and troubleshooting

The Settings window allows you to set different configurations and do some advanced actions. The settings window contains two tabs:

Settings

Option Description
Telemetry full diagnostics Sends full telemetry data to Microsoft for application improvement.
Enable Verbose Logging Enables verbose logging and network capture to be collected when exporting the logs to a zip file.

Screenshot of the macOS Settings and Troubleshooting view, with the Settings tab selected.

Troubleshooting

Action Description
Get Latest Policy Downloads and applies the latest forwarding profile for your organization.
Clear cached data Deletes the client's internal cached data related to authentication, forwarding profile, FQDNs, and IPs.
Export Logs Exports logs and configuration files related to the client to a zip file.
Advanced Diagnostics Tool An advanced tool to monitor and troubleshoot the client's behavior.

Screenshot of the macOS Settings and Troubleshooting view, with the Troubleshooting tab selected.

Known limitations

Known limitations for the current version of the Global Secure Access client include:

Secure Domain Name System (DNS)

If Secure DNS is enabled on the browser or in macOS and the DNS server supports Secure DNS, then the client doesn't tunnel traffic set to be acquired by FQDN. (Network traffic that's acquired by IP isn't affected and is tunneled according to the forwarding profile.) To mitigate the Secure DNS issue, disable Secure DNS, set a DNS server that doesn't support Secure DNS, or create rules based on IP.

IPv6 not supported

The client tunnels only IPv4 traffic. IPv6 traffic isn't acquired by the client and therefore routed directly to the network. To make sure that all traffic is routed to Global Secure Access, disable IPv6.

Connection fallback

If there's a connection error to the cloud service, the client falls back to either direct Internet connection or blocking the connection, based on the hardening value of the matching rule in the forwarding profile.

Geolocation of source IP address

For network traffic that is tunneled to the cloud service, the application server (website) detects the connection's source IP as the edge's IP address (and not as the user-device's IP address). This scenario might affect services that rely on geolocation.

Tip

For Office 365 and Entra to detect the device's true source IP, consider enabling Source IP restoration.

Virtualization support with UTM

  • When the network is in bridged mode and Global Secure Access client is installed on the host machine:
    • If the Global Secure Access client is installed on the virtual machine, network traffic of the virtual machine is subject to its local policy. The host machine's policy doesn't affect the forwarding profile on the virtual machine.
    • If the Global Secure Access client isn't installed on the virtual machine, network traffic of the virtual machine is bypassed.
  • The Global Secure Access client doesn't support network shared mode because it might block the network traffic of the virtual machine.
  • If the network is in shared mode, you can install the Global Secure Access client on a virtual machine running macOS, as long as the client isn't also installed on the host machine.

QUIC not supported for Internet Access

Since QUIC isn't yet supported for Internet Access, traffic to ports 80 UDP and 443 UDP can't be tunneled.

Tip

QUIC is currently supported in Private Access and Microsoft 365 workloads. Administrators can disable QUIC protocol on browsers, triggering clients to fall back to HTTPS over TCP, which is fully supported in Internet Access. For more information, see QUIC not supported for Internet Access.

Related content