HowToFixMe
Azure Enterprise

How to enable Private Link for Storage Account on Application Gateway

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

⚡ At a glance
BrandApplication Gateway
FamilyAzure Enterprise
CategoryMicrosoft
Guide typeHow To
Skill levelIntermediate

Why this matters

Enable private link for storage account on a Application Gateway device is one of the highest-volume how-to searches for the Azure Enterprise category. Most users find the menu path inconsistent across Application Gateway model revisions, so this guide gives a generalised path plus model-specific notes.

Pre-requisites

Step-by-step

  1. Locate the setting. Open settings on your Application Gateway device. For "enable Private Link for Storage Account", the option lives under one of: General, Advanced, Connectivity, Accessibility, or a Application Gateway-specific menu. Check the Application Gateway 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 Application Gateway 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

Common gotchas

Region / variant notes

Some Application Gateway features are region-locked or only available on higher-tier SKUs. If your variant doesn't show "enable Private Link for Storage Account" at all, check the Application Gateway model spec sheet to confirm support.

Frequently asked questions

How long should the recovery / setup take?

For most Application Gateway Azure Enterprise 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 Application Gateway model?

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

Does this affect my Application Gateway 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 worth a look while you sort this one out:

References

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

What changed recently?

Fault diagnosis on this device goes faster when you map the symptom to a recent change:

The answer narrows the root cause to a manageable subset.

Before you start

A few things to confirm so this device fix goes cleanly:

How to confirm it's actually fixed

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

Escalation guide

For the device in front of you, the right escalation depends on impact:

More frequently asked questions

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.

Why is this happening on a brand-new unit?

Out-of-box defects do occur. If you've owned the device under 30 days and the symptom persists after a tenant reset, escalate to the seller for replacement under DOA terms before opening a manufacturer support case.

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.

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.

Field notes from real Azure Enterprise incidents

When I work on enable Private Link for Storage Account on Application Gateway the rhythm I lean on is the one I have built over years of these tickets. I have lost more hours to Azure Resource Graph queries than I would like to admit, but the alternative: clicking through the portal hoping the right blade loads, is worse. Network Watcher's connectivity check has saved me from blaming Azure when the problem turned out to be a stale NSG rule someone left behind from a pilot. Activity Log is the first place I open on any Azure regression because the operation that flipped the state is usually right there at the top of the list.

Tools I actually reach for

For enable Private Link for Storage Account on Application Gateway on Application Gateway the cheapest signal I can land usually comes from Azure Portal Resource Explorer, then Network Watcher, Azure Monitor Logs (Kusto), az aks get-credentials when Azure Portal Resource Explorer cannot see the layer the fault sits in, and Azure Activity Log 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 Private Link for Storage Account on Application Gateway resolved on a Application Gateway 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.

az account show --query '{sub:id,tenant:tenantId}' -o table

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.

az network watcher test-connectivity --source-resource VM1 --dest-resource VM2

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.

az monitor activity-log list --resource-group RG --max-events 25 -o table

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.

az resource list --resource-group RG --query "[].{name:name,type:type}" -o table

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 Azure Enterprise detail, the disambiguation order I lean on is stable. I usually start at techcommunity.microsoft.com for the ground-truth view on Azure Enterprise. I usually start at azurecharts.com for the ground-truth view on Azure Enterprise. I usually start at azure.microsoft.com/updates for the ground-truth view on Azure Enterprise. I usually start at learn.microsoft.com/azure for the ground-truth view on Azure Enterprise. 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 Private Link for Storage Account on Application Gateway have a habit of biting back. The pitfalls below are the ones I have personally walked into on a Application Gateway unit, not things I read about. Activity Log is the first place I open on any Azure regression because the operation that flipped the state is usually right there at the top of the list. Network Watcher's connectivity check has saved me from blaming Azure when the problem turned out to be a stale NSG rule someone left behind from a pilot. I have lost more hours to Azure Resource Graph queries than I would like to admit, but the alternative. clicking through the portal hoping the right blade loads, is worse. 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 Private Link for Storage Account on Application Gateway off to the next person on rotation, the three lines I leave in the runbook are these. First, the symptom signature for Application Gateway on the Azure Enterprise 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 Private Link for Storage Account on Application Gateway on a Application Gateway 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.