Live Migration Supportability for Guest TPM–Enabled VMs on Azure Local (v24h2) Cluster
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- azure
- Domain
- cloud, infrastructure
Research direction
Review the linked Azure Local trusted launch automatic state transfer documentation and the Windows Server Host Guardian Service documentation. Determine whether live migration and HGS are supported for Guest TPM-enabled VMs on Azure Local v24H2, including prerequisites and limitations; done means providing official Microsoft guidance for all three questions.
Written by the indexing model from the issue text.
Description
Hello Team,
Is it possible to live migrate (without shutdown) Guest TPM-enabled virtual machines between hosts in an Azure Local (Azure Stack HCI) v24H2 cluster?
Context:
These VMs are critical, and shutdown is not preferred during:
Monthly patching, Cluster node maintenance
From current documentation, moving a Guest TPM-enabled VM appears to require shutdown migration.
https://learn.microsoft.com/en-us/azure/azure-local/manage/trusted-launch-automatic-state-transfer?view=azloc-2512
Questions:
1)Is live migration supported for Guest TPM-enabled VMs in Azure Local v24H2, or is shutdown migration the only supported option?
2) Is Host Guardian Service (HGS) supported with Azure Local clusters to enable live migration?
3) HGS documentation lists Windows Server editions (2016–2025), but Azure Local is not explicitly mentioned. Is HGS officially supported on Azure Local v24H2, and are there any limitations or prerequisites?
https://learn.microsoft.com/en-us/windows-server/security/guarded-fabric-shielded-vm/guarded-fabric-manage-hgs
Any official guidance or documentation from Microsoft would be appreciated.
Thank you.
- Dominant language
- PowerShell
- Stars
- 79
- Forks
- 60
- Avg merge
- 5h 24m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/AzureLocal-Supportability
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Azure/AzureLocal-Supportability#253 · 1 comment ·
All issues in Azure/AzureLocal-Supportability
Similar issues
-
bug status/needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
prowler-cloud/prowler#12885 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
nasa/cumulus-process-py#156 ·
-
bug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
pnp/pnpcore#1878 · 1 comment ·
Maintainers usually reply within 1 day
-
render.yamlOpen
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
[BUG] `RunsArtifactRepository.download_artifacts` reports artifact store errors as a wrong pathOpenarea/tracking
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day