You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Azure Operator Nexus (formerly called AODS, as denoted in #411) has specific connectivity and security requirements that are both a subset and a superset of the Landing Zone concept as defined in the Cloud Adoption Framework. The references to Nexus and how it fits into the overall picture need to be updated accordingly.
Feature or Idea - Why?
This issue is meant to provide visibility on the fact that this is being tracked and discussed in order for Microsoft and partners to be able to provide specific guidance on the relationship between a Nexus deployment and existing Landing Zones (if any) and how both platform requirements and hybrid workload requirements align with our industry reference architectures.
Feature or Idea - What?
Azure Operator Nexus (formerly called AODS, as denoted in #411) has specific connectivity and security requirements that are both a subset and a superset of the Landing Zone concept as defined in the Cloud Adoption Framework. The references to Nexus and how it fits into the overall picture need to be updated accordingly.
Feature or Idea - Why?
This issue is meant to provide visibility on the fact that this is being tracked and discussed in order for Microsoft and partners to be able to provide specific guidance on the relationship between a Nexus deployment and existing Landing Zones (if any) and how both platform requirements and hybrid workload requirements align with our industry reference architectures.
Code of Conduct