Skip to content

docs(kb): add field alert for Azure MANA hardware incompatibility - #1199

Merged
agrawalkaushik merged 5 commits into
masterfrom
kagrawal/azure-mana-field-alert
Oct 20, 2026
Merged

agrawalkaushik merged 5 commits into
masterfrom
kagrawal/azure-mana-field-alert

Conversation

@agrawalkaushik

Copy link
Copy Markdown
Contributor

Summary

Adds a new Knowledge Base field alert article documenting a hardware compatibility issue affecting virtual Session Smart Router (vSSR) deployments in Microsoft Azure.

Details

  • Issue: Microsoft is rolling out Azure host hardware based on the Microsoft Azure Network Adapter (MANA). vSSR instances placed on MANA-enabled hardware do not function, as current SSR software lacks native MANA support.
  • Affected Deployments: vSSR instances running as Network Virtual Appliances (NVAs) in Microsoft Azure. Placement on MANA-enabled hardware can occur during new deployments, VM stop/deallocate/restart, VM redeployment, or Azure host maintenance/relocation events.
  • Workaround: Apply the Microsoft LegacyVMNVA opt-out tag to keep affected vSSR instances on current (non-MANA) hardware. This opt-out mechanism is available through May 31, 2027.
  • Resolution: Native MANA support is targeted for SSR version 7.3.3-r2 or above. Customers should plan upgrades to that version ahead of the opt-out expiration deadline.

The article includes problem description, affected deployment details, symptom/cause analysis, required customer actions, upgrade planning guidance, and an FAQ section.

Checklist

  • New KB markdown file added under kb/
  • Frontmatter includes title, date, tags
  • Content reviewed for accuracy against advisory details

Add new KB field alert article covering virtual Session Smart Router
(vSSR) incompatibility with Microsoft Azure Network Adapter (MANA)
enabled hardware.

- Describes impact on vSSR instances placed on MANA-enabled Azure
  hosts, which fail to function until native MANA support ships.
- Documents the Microsoft LegacyVMNVA opt-out tag as the recommended
  workaround, available through the May 31, 2027 deadline.
- Notes target SSR version 7.3.3-r2 or above for native MANA support
  and provides upgrade planning guidance.
- Includes affected deployment details, symptom/cause analysis, and
  an FAQ section for customer-facing clarity.

Co-authored-by: Copilot App <[email protected]>

@Chr1st0ph3rTurn3r Chr1st0ph3rTurn3r left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I find this KB VERY confusing. I will work with Kaushik and Sam to clarify.

@Chr1st0ph3rTurn3r
Chr1st0ph3rTurn3r self-requested a review October 20, 2026 16:57
@agrawalkaushik
agrawalkaushik merged commit 10d5d3c into master Oct 20, 2026
1 of 2 checks passed
@agrawalkaushik
agrawalkaushik deleted the kagrawal/azure-mana-field-alert branch October 20, 2026 21:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants