How to migrate ADFS to Entra ID with migration tool on Global Secure Access

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

Why this matters

Migrate adfs to entra id with migration tool on a Global Secure Access device is one of the highest-volume how-to searches for the Entra Identity category. Most users find the menu path inconsistent across Global Secure Access model revisions, so this guide gives a generalised path plus model-specific notes.

Pre-requisites

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

Step-by-step

1. Locate the setting. Open settings on your Global Secure Access device. For "migrate ADFS to Entra ID with migration tool", the option lives under one of: General, Advanced, Connectivity, Accessibility, or a Global Secure Access-specific menu. Check the Global Secure Access 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 Global Secure Access 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 Global Secure Access 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 Global Secure Access app process. Whitelist it.
• Feature works but with delay. usually cloud-sync latency; check internet speed and Global Secure Access service status.

Region / variant notes

Some Global Secure Access features are region-locked or only available on higher-tier SKUs. If your variant doesn't show "migrate ADFS to Entra ID with migration tool" at all, check the Global Secure Access model spec sheet to confirm support.

Frequently asked questions

How long should the recovery / setup take?

For most Global Secure Access 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 Global Secure Access model?

The procedure reflects current Global Secure Access 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. Global Secure Access doesn't usually publish rollback procedures, so make sure you can restore manually.

Does this affect my Global Secure Access 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:

• How to migrate ADFS to Entra ID with migration tool on Access Reviews
• How to migrate ADFS to Entra ID with migration tool on Conditional Access
• How to migrate ADFS to Entra ID with migration tool on Entitlement Management
• How to migrate ADFS to Entra ID with migration tool on Entra B2B / B2C
• How to migrate ADFS to Entra ID with migration tool on Entra Connect / Cloud Syn
• How to migrate ADFS to Entra ID with migration tool on Entra ID (Azure AD)

References

• Global Secure Access official support portal for your model.
• Global Secure Access 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 the device in front of you, 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.

Before you start

A few things to confirm so the affected device fix goes cleanly:

• Latest service version downloaded if you're going to update.
• support coverage + support contract status checked, opening managed parts may void it.
• Backup of current configuration (where applicable) taken.
• Spare parts on hand if you anticipate replacement.
• Adequate workspace, lighting, and time: rushing causes regressions.

Quick verification

Before you walk away from this unit fix, run through:

1. Reproduce the original trigger, does the issue reappear? 2. Check the device's status / health screen for any new alerts. 3. Confirm paired devices (app, hub, controller) reconnected. 4. Save / commit any configuration changes per the device's normal workflow. 5. Note the change in your maintenance log with date + service version version.

Escalation guide

For the affected device, the right escalation depends on impact:

• Cosmetic / minor: log a ticket via the How app or web portal. Response 1-3 business days.
• Mid-impact: phone support. Have your serial number ready.
• Critical (production down, safety issue): in-person dealer / TAC visit. Bring proof of purchase.
• Out of support coverage: third-party repair shop with manufacturer-certified technicians.

More frequently asked questions

Should I update service version first or last?

Update service version first if a release note specifically mentions your symptom. Otherwise, finish the troubleshooting flow first, then update; that way you can isolate whether the update or the underlying fix solved it.

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.

How often should I run preventive checks?

Quarterly for most consumer devices; monthly for production / commercial devices. Set a calendar reminder so the device stays healthy between issues.

Will this void my support coverage?

Applying official service version updates and following the user manual will not affect support coverage. Opening managed services, jumping safety circuits, or using third-party parts can void support coverage in most jurisdictions.

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).

Field notes from real Entra Identity incidents

When I work on migrate ADFS to Entra ID with migration tool on Global Secure Access the rhythm I lean on is the one I have built over years of these tickets. 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. The Microsoft Graph PowerShell SDK is the path forward for Entra automation; the legacy AzureAD module is on a timer.

Tools I actually reach for

For migrate ADFS to Entra ID with migration tool on Global Secure Access on Global Secure Access the cheapest signal I can land usually comes from Entra admin center, then Entra ID Diagnostics & Logs, Audit logs, Sign-in logs when Entra admin center cannot see the layer the fault sits in, and Microsoft Graph PowerShell SDK 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 migrate ADFS to Entra ID with migration tool on Global Secure Access resolved on a Global Secure Access 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.

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.

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.

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.

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 azure.microsoft.com/updates for the ground-truth view on Entra Identity. 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. 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 migrate ADFS to Entra ID with migration tool on Global Secure Access have a habit of biting back. The pitfalls below are the ones I have personally walked into on a Global Secure Access 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. The Microsoft Graph PowerShell SDK is the path forward for Entra automation; the legacy AzureAD module is on a timer. 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 migrate ADFS to Entra ID with migration tool on Global Secure Access off to the next person on rotation, the three lines I leave in the runbook are these. First, the symptom signature for Global Secure Access 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 migrate ADFS to Entra ID with migration tool on Global Secure Access on a Global Secure Access 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.