[Wiki] Smaller fixes / suggestions (#1223)
Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
This commit is contained in:
Alexander Sehr
GitHub
Родитель
accbe5d272
Коммит
ab3748874d
|
|
@ -11,9 +11,9 @@ It is important to highlight that not all enterprises adopt Azure in the same wa
|
|||
|
||||
## Landing Zones Definition
|
||||
|
||||
Within the context of the Enterprise-Scale architecture, a "Landing Zone" is a logical construct capturing everything that must be true to enable application migrations and development at an Enterprise-Scale in Azure. It considers all platform Resources that are required to support the customer's application portfolio and does not differentiate between IaaS or PaaS.
|
||||
Within the context of the Enterprise-Scale architecture, a "Landing Zone" is a logical construct capturing everything that must be true to enable application migrations and development at an Enterprise-Scale in Azure. It considers all platform resources that are required to support the customer's application portfolio and does not differentiate between IaaS or PaaS.
|
||||
|
||||
Every large enterprise software estate will encompass a myriad of application archetypes and each Landing Zone essentially represents the common elements, such as networking and IAM, that are shared across instances of these archetypes and must be in place to ensure that migrating applications have access to requisite components when deployed. Each Landing Zone must consequently be designed and deployed in accordance with the requirements of archetypes within the customer's application portfolio.
|
||||
Every large enterprise software estate will encompass a myriad of application archetypes and each Landing Zone essentially represents the common elements, such as networking and IAM, that are shared across instances of these archetypes and must be in place to ensure that migrated applications have access to requisite components when deployed. Each Landing Zone must consequently be designed and deployed in accordance with the requirements of archetypes within the customer's application portfolio.
|
||||
|
||||
The principle purpose of the "Landing Zones" is therefore to ensure that when an application lands on Azure, the required "plumbing" is already in place, providing greater agility and compliance with enterprise security and governance requirements.
|
||||
|
||||
|
|
|
|||
|
|
@ -14,23 +14,22 @@ The Enterprise-Scale architecture is modular by design and allow organizations o
|
|||
|
||||
The Enterprise-Scale reference implementations support Azure adoption at scale and provides guidance and architecture based on the authoritative design for the Azure platform as a whole.
|
||||
|
||||
Enterprise-Scale reference implementations are tying together all the Azure platform primitives and creates a proven, well-defined Azure architecture based on a multi-subscription design, leveraging native platform capabilities to ensure organizations can create and operationalize their landing zones in Azure at scale.
|
||||
Enterprise-Scale reference implementations are tying together all the Azure platform primitives and create a proven, well-defined Azure architecture based on a multi-subscription design, leveraging native platform capabilities to ensure organizations can create and operationalize their landing zones in Azure at scale.
|
||||
|
||||
The following table outlines key customer requirements in terms of landing zones, and how it is they are being addressed with Enterprise-Scale:
|
||||
|
||||
| **Key customer landing zone requirement** | **Enterprise-Scale reference implementations** |
|
||||
| ------------------------------------------------------------ | ------------------------------------------------------------ |
|
||||
| Timelines to reach security and compliance requirements for a workload | Enabling all recommendations during setup, will ensure resources are compliant from a monitoring and security perspective |
|
||||
| Provides a baseline architecture using multi-subscription design | Yes, for the entire Azure tenant regardless of customer’s scale-point |
|
||||
| Best-practices from cloud provider | Yes, proven and validated with customers |
|
||||
| Be aligned with cloud provider’s platform roadmap | Yes |
|
||||
| UI Experience and simplified setup | Yes, Azure portal |
|
||||
| All critical services are present and properly configured according to recommend best practices for identity & access management, governance, security, network and logging | Yes, using a multi-subscription design, aligned with Azure platform roadmap |
|
||||
| Automation capabilities (IaC/DevOps) | Yes: ARM, Azure Policy, GitHub/Azure DevOps CI/CD pipeline options included |
|
||||
| Provides long-term self-sufficiency | Yes, Enterprise-scale architecture -> 1:N landing zones. Approach & architecture prepare the customer for long-term self-sufficiency;, the RIs reference implementations are there to get you started |
|
||||
| Enables migration velocity across the organization | Yes, Enterprise-scale Scale architecture -> 1:N landing zones., Architecture includes designs for segmentation and separation of duty to empower teams to act within appropriate landing zones |
|
||||
| Achieves operational excellence | Yes. Enables autonomy for platform and application teams with a policy driven governance and management |
|
||||
|
||||
| **Key customer landing zone requirement** | **Enterprise-Scale reference implementations** |
|
||||
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Timelines to reach security and compliance requirements for a workload | Yes. Enabling all recommendations during setup will ensure resources are compliant from a monitoring and security perspective |
|
||||
| Provides a baseline architecture using multi-subscription design | Yes. For the entire Azure tenant regardless of customer's scale-point |
|
||||
| Best-practices from cloud provider | Yes. Proven and validated with customers |
|
||||
| Be aligned with cloud provider's platform roadmap | Yes. |
|
||||
| UI Experience and simplified setup | Yes. Via the Azure portal |
|
||||
| All critical services are present and properly configured according to recommended best practices for identity & access management, governance, security, network and logging | Yes. Using a multi-subscription design, aligned with Azure platform roadmap |
|
||||
| Automation capabilities (IaC/DevOps) | Yes. ARM/Bicep, Terraform, Azure Policy, GitHub/Azure DevOps CI/CD pipeline options included |
|
||||
| Provides long-term self-sufficiency | Yes. Enterprise-scale architecture -> 1:N landing zones. Approach & architecture prepare the customer for long-term self-sufficiency. The RIs reference implementations are there to get you started |
|
||||
| Enables migration velocity across the organization | Yes. Enterprise-scale Scale architecture -> 1:N landing zones. Architecture includes designs for segmentation and separation of duty to empower teams to act within appropriate landing zones |
|
||||
| Achieves operational excellence | Yes. Enables autonomy for platform and application teams with a policy-driven governance and management |
|
||||
## Pricing
|
||||
|
||||
There’s no cost associated with Enterprise-Scale itself, as it is just an architecture that is constructed using existing Azure products and services. Therefore you only pay for the Azure products and services that you choose to enable, and also the products and services your organization will deploy into the landing zones for your workloads.
|
||||
|
|
|
|||
|
|
@ -4,8 +4,8 @@
|
|||
"metadata": {
|
||||
"_generator": {
|
||||
"name": "bicep",
|
||||
"version": "0.14.6.61914",
|
||||
"templateHash": "4092169081838784302"
|
||||
"version": "0.14.46.61228",
|
||||
"templateHash": "7060229439476035488"
|
||||
}
|
||||
},
|
||||
"parameters": {
|
||||
|
|
|
|||
|
|
@ -4,8 +4,8 @@
|
|||
"metadata": {
|
||||
"_generator": {
|
||||
"name": "bicep",
|
||||
"version": "0.14.6.61914",
|
||||
"templateHash": "13556197755507967292"
|
||||
"version": "0.14.46.61228",
|
||||
"templateHash": "2601801354196210891"
|
||||
}
|
||||
},
|
||||
"variables": {
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче