How to enable Global Secure Access tenant on Entra Connect / Cloud Sync

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

Why this matters

Enable global secure access tenant on a Entra Connect / Cloud Sync device is one of the highest-volume how-to searches for the Entra Identity category. Most users find the menu path inconsistent across Entra Connect / Cloud Sync model revisions, so this guide gives a generalised path plus model-specific notes.

Pre-requisites

• A Entra Connect / Cloud Sync device that's powered on and on the latest stable service version / OS.
• The Entra Connect / Cloud Sync companion app or management tool installed and signed in.
• 5-15 minutes uninterrupted.

Step-by-step

1. Locate the setting. Open settings on your Entra Connect / Cloud Sync device. For "enable Global Secure Access tenant", the option lives under one of: General, Advanced, Connectivity, Accessibility, or a Entra Connect / Cloud Sync-specific menu. Check the Entra Connect / Cloud Sync user manual for your exact model if you can't find it.
2. Toggle the feature on. Confirm the on-screen prompt.
3. Configure sub-options. Most features have 2-3 sub-options (mode, schedule, paired device). Pick values that match your real-world usage pattern.
4. Save / apply. Some Entra Connect / Cloud Sync models auto-save, others require an explicit Done / Save tap.
5. Test live. Trigger the feature in a real scenario to confirm the configuration is correct.

Tips that save time

• Pair this feature with a Entra Connect / Cloud Sync automation / routine if the device supports it.
• If the feature relies on cloud sync, give it 1-2 minutes after enabling to propagate.
• For multi-user households / multi-admin teams, set per-user profiles so each user sees their preferred state.

Common gotchas

• Feature greyed out, usually service version too old. Update + retry.
• Feature works once then stops: battery saver / power saver mode is killing the Entra Connect / Cloud Sync app process. Whitelist it.
• Feature works but with delay, usually cloud-sync latency; check internet speed and Entra Connect / Cloud Sync service status.

Region / variant notes

Some Entra Connect / Cloud Sync features are region-locked or only available on higher-tier SKUs. If your variant doesn't show "enable Global Secure Access tenant" at all, check the Entra Connect / Cloud Sync model spec sheet to confirm support.

Frequently asked questions

How long should the recovery / setup take?

For most Entra Connect / Cloud Sync Entra Identity cases, allow 15-45 minutes the first time. Repeats are usually under 10 minutes once you know the menu path.

Will this exact procedure work on every Entra Connect / Cloud Sync model?

The procedure reflects current Entra Connect / Cloud Sync behaviour. Menu paths shift between service version generations; verify against the manual for your specific model + revision.

Is the procedure safe in production / live use?

Apply during a maintenance window where possible. Capture pre-change state. Entra Connect / Cloud Sync doesn't usually publish rollback procedures, so make sure you can restore manually.

Does this affect my Entra Connect / Cloud Sync support coverage?

Standard operation per the user manual + applying official service version updates does NOT void support coverage. Opening managed services, third-party repair, or unauthorised modifications can void support coverage. check before going further.

Related guides

• All Entra Identity guides → /microsoft/section/entra_identity.html
• All Microsoft guides → /microsoft/

Related fixes

Related guides worth a look while you sort this one out:

• Entra Connect / Cloud Sync B2B cross tenant access settings inbound blocked: Fix
• How to enable Global Secure Access tenant on Access Reviews
• How to enable Global Secure Access tenant on Conditional Access
• How to enable Global Secure Access tenant on Entitlement Management
• How to enable Global Secure Access tenant on Entra B2B / B2C
• How to enable Global Secure Access tenant on Entra ID (Azure AD)

References

• Entra Connect / Cloud Sync official support portal for your model.
• Entra Connect / Cloud Sync community forum + Reddit threads.
• Vendor PSIRT / advisory page (where applicable).

Reference material, not professional advice. Validate with your vendor manual and follow local regulations.

Common patterns we see

When this symptom shows up on this unit, three patterns repeat:

1. Recent service version update changed behavior, the symptom started within a week of an OTA push. Rollback or wait for the hotfix. 2. Environmental trigger: temperature, humidity, line voltage, network changes. Look at what changed in the environment. 3. Cumulative wear, components like batteries, gaskets, fans degrade over time. Replace the consumable rather than chasing a software fix.

Knowing which pattern applies saves time on the wrong fix.

Safety + preconditions

Before any work on the affected device:

• Unplug from mains for any internal-access procedure.
• flush cached state (circuit breakers in PSUs, residual battery charge) per manufacturer guidance.
• Use ESD-safe handling for boards and modules. no carpet, no wool sleeves.
• Avoid moisture; never apply liquids near vents or connectors.
• If you smell smoke, see scorch marks, or feel uneven heat, stop and escalate.

How to confirm it's actually fixed

On this device, the test is rarely "reboot and see". Use this list:

• Active reproduction: trigger the original failure path on purpose.
• Indirect reproduction: do an activity that would expose the same subsystem.
• Status indicator review: every service health indicator / display / app status should be green.
• 24-hour soak: leave the device under normal load overnight; check the next morning.
• Telemetry check: review the device or app's diagnostic log for new error entries.

When to call How support instead

Escalate if:

• The same symptom returns within 24 hours of a clean fix.
• You see physical damage (burn marks, swollen battery, cracked PCB).
• The device is in support coverage and a hardware replacement is the cheaper outcome.
• Repair requires specialised tools you don't own (alignment jigs, calibration software).
• Following the official path keeps the support coverage intact, which matters more than the time spent.

More frequently asked questions

Are there safer alternatives for non-technical users?

Yes, the manufacturer's self-service troubleshooter (HP Smart, LG ThinQ, Samsung Members, similar) usually walks through the same steps in a guided UI. Use that first if you're not comfortable with menu paths.

Does this affect other devices on my network?

Generally no. The procedure is local to this device. Network-side changes (service version updates that affect TLS, SMB, or routing) are flagged explicitly in the steps.

What if the fix returns after a reboot?

Persistent fault returns mean either: a hardware fault (escalate), a configuration that's being overwritten by a sync source (check cloud profiles), or a regression in a recent service version update (rollback).

How long does this fix usually take?

Most users complete the steps in 20-45 minutes the first time, and 5-10 minutes on subsequent runs once the menu paths are familiar.

Is it safe to apply during business hours?

If the device is in production use, apply during a scheduled maintenance window. Most procedures need 2-15 minutes of downtime. Capture pre-change state so you can roll back if needed.

Field notes from real Entra Identity incidents

When I work on enable Global Secure Access tenant on Entra Connect / Cloud Sync the rhythm I lean on is the one I have built over years of these tickets. The Microsoft Graph PowerShell SDK is the path forward for Entra automation; the legacy AzureAD module is on a timer. Sign-in logs are the single highest-signal Entra surface: every failure has a specific status code and the doc page for that code is one search away. Conditional Access What-If is the only safe way to test a policy change; deploying first and watching the support queue light up is the dangerous way.

Tools I actually reach for

For enable Global Secure Access tenant on Entra Connect / Cloud Sync on Entra Connect / Cloud Sync the cheapest signal I can land usually comes from Entra ID Diagnostics & Logs, then Entra admin center, Microsoft Graph PowerShell SDK when Entra ID Diagnostics & Logs cannot see the layer the fault sits in, and Audit logs for the cases where neither of those answers cleanly. That ordering is not academic. It matches the layers the failure tends to surface through, so the cheap signal lands first and the heavier tooling only comes out when the simpler answer does not hold up under scrutiny.

Verification I run before I close the ticket

Before I mark enable Global Secure Access tenant on Entra Connect / Cloud Sync resolved on a Entra Connect / Cloud Sync unit, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheap checks gate the more expensive ones.

Get-MgAuditLogSignIn -Top 25 -Filter "createdDateTime gt 2026-05-01T00:00:00Z"

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

Connect-MgGraph -Scopes 'AuditLog.Read.All','Directory.Read.All'

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

Entra > Diagnose and solve problems > run the relevant playbook

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

Get-MgConditionalAccessPolicy | Select-Object DisplayName,State

Only when every line above runs clean do I close the ticket and update the runbook with the timestamps.

Where I check first when the docs disagree

When two sources contradict each other on a Entra Identity detail, the disambiguation order I lean on is stable. I usually start at techcommunity.microsoft.com/category/azure-active-directory for the ground-truth view on Entra Identity. I usually start at learn.microsoft.com/entra for the ground-truth view on Entra Identity. I usually start at azure.microsoft.com/updates for the ground-truth view on Entra Identity. Random blog posts and reseller wikis are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim.

Pitfalls I have walked into on this exact path

The shortcuts that look smart on enable Global Secure Access tenant on Entra Connect / Cloud Sync have a habit of biting back. The pitfalls below are the ones I have personally walked into on a Entra Connect / Cloud Sync unit, not things I read about. Conditional Access What-If is the only safe way to test a policy change; deploying first and watching the support queue light up is the dangerous way. Sign-in logs are the single highest-signal Entra surface, every failure has a specific status code and the doc page for that code is one search away. When in doubt I revert to the slower path that the manual prescribes - the time I save by skipping it is always smaller than the time I spend cleaning up afterwards.

What I tell the next on-call

When I hand enable Global Secure Access tenant on Entra Connect / Cloud Sync off to the next person on rotation, the three lines I leave in the runbook are these. First, the symptom signature for Entra Connect / Cloud Sync on the Entra Identity family - not a paraphrase, the exact string that surfaces. Second, the diagnostic that gave the highest signal in the least time. Third, the exact verification command whose green output justified closing the ticket. That trio is what turns a one-off fix into a runbook entry the next engineer can use without paging me at three in the morning.

I also add a one-line note on the cost of getting this wrong. For enable Global Secure Access tenant on Entra Connect / Cloud Sync on a Entra Connect / Cloud Sync unit, the cost is rarely the replacement part. It is the downtime, the second site visit, and the trust deficit you spend with whoever owns the asset when the fix does not hold. That framing keeps the next on-call from choosing the cheap-looking shortcut that ends up costing the most in elapsed hours and goodwill.