[khuyentran1401]

Reference Issues or PRs

Closes #777.

What does this implement/fix?

• Replaces the "Planned" stub with a full Azure guide that follows the same structure as the AWS and Hetzner pages: prerequisites, cost, configuration, deploy, sign-in, update, upgrade, and destroy.
• Marks Azure as supported in the provider table.
• Updates the enterprise TLS proxy note, which said the Azure provider was not built yet.

Testing

• Did you test the pull request locally?

• Did you add new tests?

• Checked fields, defaults, and destroy behavior against the nic source (447ed13) and the aks-cluster module (v0.3.0).

• Sign-in with az login plus AZURE_SUBSCRIPTION_ID confirmed by a successful nic deploy --dry-run.

• Not tested with a full deploy, so the load balancer and public IP cost items are still unconfirmed.

[github-actions]

Docs preview for docs/azure-provider-page:

• Nebari (via the nebari-docs Worker): https://docs-azure-provider-page-nebari-docs.openteams-account.workers.dev
• Nebari Classic (via the nebari-docs-classic Worker): https://docs-azure-provider-page-nebari-docs-classic.openteams-account.workers.dev

[dcmcand]

Verdict: Comment. I checked the page against nic 82753a6 and aks-cluster v0.3.0, and the claims hold, with the corrections inline. None of them block.

💡 Suggestion: The page marks Azure supported but does not list two limitations that a user will hit. Add a short Limitations section.

• Longhorn is not installed on Azure, so Longhorn backups do not work (provider.go:392-396; backup-restore.md already says this).
• The enterprise TLS trust_bundle is not installed on Azure nodes, and nic gives no warning.

💡 Suggestion: upgrade-kubernetes.md links the AWS and Hetzner pages for provider-specific upgrade constraints. Add this page there too.

---

Key: 🛑 Blocker (must fix before merge) · 💡 Suggestion (improvement, not blocking) · ❓ Question (needs author input) · ❤️ Kudos