Merge pull request #5904 from MicrosoftDocs/main

10/18/2024 AM Publish

.openpublishing.redirection.scenarios.json

@@ -243,7 +243,7 @@
     {
       "source_path": "docs/scenarios/data-management/secure.md",
       "redirect_url": "/azure/cloud-adoption-framework/scenarios/cloud-scale-analytics/secure",
-      "redirect_document_id": true
+      "redirect_document_id": false
     },
     {
       "source_path": "docs/scenarios/data-management/security-provisioning.md",
@@ -318,7 +318,7 @@
     {
       "source_path": "docs/scenarios/data-management/best-practices/sap-data-ingestion.md",
       "redirect_url": "/azure/cloud-adoption-framework/scenarios/cloud-scale-analytics/best-practices/sap-data-ingestion",
-      "redirect_document_id": true
+      "redirect_document_id": false
     },
     {
       "source_path": "docs/scenarios/aks/azure-products.md",
@@ -439,6 +439,21 @@
       "source_path": "docs/scenarios/cloud-scale-analytics/architectures/reference-architecture-relecloud.md",
       "redirect_url": "/azure/cloud-adoption-framework/scenarios/cloud-scale-analytics/architectures/reference-architecture-multizone",
       "redirect_document_id": true
+    },
+    {
+      "source_path": "docs/scenarios/cloud-scale-analytics/security-provisioning.md",
+      "redirect_url": "/azure/cloud-adoption-framework/scenarios/cloud-scale-analytics/secure",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "docs/scenarios/cloud-scale-analytics/best-practices/sap-data-ingestion.md",
+      "redirect_url": "/azure/cloud-adoption-framework/scenarios/sap/sap-lza-choose-azure-connectors",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "docs/scenarios/cloud-scale-analytics/best-practices/data-lake-access.md",
+      "redirect_url": "/azure/storage/blobs/data-lake-storage-access-control-model",
+      "redirect_document_id": false
     }
   ]
 }

docs/innovate/index.md

@@ -3,7 +3,7 @@ title: Cloud adoption-related innovation
 description: Learn how cloud adoption-related innovation can provide business value by unlocking new technical skills and expanded business capabilities.
 author: martinekuan
 ms.author: martinek
-ms.date: 08/25/2022
+ms.date: 10/14/2024
 ms.topic: conceptual
 ms.custom: internal, ai-learning-hub
 keywords: cloud innovation, cloud adoption, cloud framework, cloud adoption framework
@@ -20,7 +20,7 @@ To prepare for this phase of the cloud adoption lifecycle, the framework suggest
 | <span title="icon">&nbsp;</span> | <span title="description">&nbsp;</span> |
 |--|--|
 | <br> :::image type="icon" source="../_images/icons/1.png"::: | <br> [Create hypothesis with business value consensus](./business-value.md): Before you decide on technical solutions, identify how new innovations can drive business value and come up with a hypothesis about customer needs. |
-| <br> :::image type="icon" source="../_images/icons/2.png"::: | <br> [Build your first MVP](./considerations/build.md): Once you have a hypothesis with enough value potential to integrate it into your application, start the build process. Development sprints should be as quick as possible. Quick sprints let teams quickly verify or reject a hypothesis, or fine tune how required functionality integrates with the application.  |
+| <br> :::image type="icon" source="../_images/icons/2.png"::: | <br> [Build your first MVP](./considerations/build.md): Once you have a hypothesis with enough value potential to integrate it into your application, start the build process. Development sprints should be as quick as possible. Quick sprints let teams quickly verify or reject a hypothesis, or fine tune how required functionality integrates with the application. |
 | <br> :::image type="icon" source="../_images/icons/3.png"::: | <br> [Measure](./considerations/measure.md) & [Learn](./considerations/learn.md) from your MVP: You want to verify the accuracy of your hypothesis as soon as possible. A minimum viable product (MVP) is a preliminary version of the new feature that offers enough functionality to gather feedback and confirm if you're moving in the right direction. |
 | <br> :::image type="icon" source="../_images/icons/4.png"::: | <br> [Expand digital innovation](./considerations/invention.md): To refine your hypothesis using the innovation disciplines or the digital inventions that include: <li> Democratize data <li> Engage via applications <li> Empower adoption <li> Interact with devices <li> Predict and influence
 
@@ -49,7 +49,7 @@ The following section describes the formula for innovation and the commitments i
 
 ## Formula for innovation
 
-Successful innovation isn't about some big transformational event or an elusive, mythical process. Success in innovation is more of a balancing act, illustrated by a simple equation: **innovation = invention + adoption**.
+Successful innovation isn't about some significant transformational event or an elusive, mythical process. Success in innovation is more of a balancing act, illustrated by a simple equation: **innovation = invention + adoption**.
 
 Innovation happens at the intersection of invention and adoption. True innovation stems from slowly adjusting human experiences through new approaches, new processes, and new technologies. In this formula, invention means you create a new solution that meets a customer need. Conversely, adoption means you apply the new solution to shape human behaviors and interactions. Finding the right balance between invention and adoption requires iteration, data-driven decision making, constant learning, and a growth mindset. It also requires technologies that can keep pace with the countless opportunities to learn in today's digital society.
 

docs/manage/azure-management-guide/inventory.md

@@ -3,7 +3,7 @@ title: Inventory and visibility in Azure
 description: Learn the tools that provide both an inventory and visibility into the inventory's run state to collect operational data.
 author: martinekuan
 ms.author: martinek
-ms.date: 10/17/2019
+ms.date: 10/14/2024
 ms.topic: conceptual
 ms.custom: internal, fasttrack-edit, AQC
 ---
@@ -42,7 +42,7 @@ For any enterprise-grade environment, the following table outlines the suggested
 
 Azure Service Health provides a personalized view of the health of your Azure services and regions. Information about active issues is posted to Azure Service Health to help you understand the effect on your resources. Regular updates keep you informed as issues are resolved.
 
-We also publish planned maintenance events to Azure Service Health so you'll know about changes that can affect resource availability. Set up Service Health alerts to notify you when service issues, planned maintenance, or other changes might affect your Azure services and regions.
+We also publish planned maintenance events to Azure Service Health so you know about changes that can affect resource availability. Set up Service Health alerts to notify you when service issues, planned maintenance, or other changes might affect your Azure services and regions.
 
 Azure Service Health includes:
 
@@ -85,7 +85,7 @@ Azure Monitor provides a single unified hub for all monitoring and diagnostics d
 
 - **Monitor and visualize metrics.** Metrics are numerical values available from Azure resources. They help you understand the health of your systems. Customize charts for your dashboards, and use workbooks for reporting.
 
-- **Query and analyze logs.** Logs include activity logs and diagnostic logs from Azure. Collect additional logs from other monitoring and management solutions for your cloud or on-premises resources. Log Analytics provides a central repository to aggregate all of this data. From there, you can run queries to help troubleshoot issues or to visualize data.
+- **Query and analyze logs.** Logs include activity logs and diagnostic logs from Azure. Collect more logs from other monitoring and management solutions for your cloud or on-premises resources. Log Analytics provides a central repository to aggregate all of this data. From there, you can run queries to help troubleshoot issues or to visualize data.
 
 - **Set up alerts and actions.** Alerts notify you of critical conditions. Corrective actions can be taken based on triggers from metrics, logs, or service-health issues. You can set up different notifications and actions and can also send data to your IT service management tools.
 
@@ -103,7 +103,7 @@ Start monitoring your:
 - [Virtual machines](/azure/azure-monitor/vm/service-map)
 - [Networks](/azure/networking/network-monitoring-overview)
 
-To monitor other resources, find additional solutions in Azure Marketplace.
+To monitor other resources, find other solutions in Azure Marketplace.
 
 To explore Azure Monitor, go to the [Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_Monitoring/AzureMonitoringBrowseBlade/overview).
 

docs/ready/considerations/development-strategy-development-lifecycle.md

@@ -3,7 +3,7 @@ title: Development lifecycle
 description: Design area guidance for DevOps principles and practices in Azure Landing Zones
 author: elanzel
 ms.author: elanzelm
-ms.date: 06/18/2022
+ms.date: 10/14/2024
 ms.topic: conceptual
 ms.custom: internal
 ---
@@ -43,9 +43,9 @@ Development lifecycle strategy provides key design considerations and recommenda
 
 - Use private repositories when building Azure Landing Zones
 
-- Use public repositories when sharing non-confidential information like automation examples, public documentation, and open-source collaboration material.
+- Use public repositories when sharing nonconfidential information like automation examples, public documentation, and open-source collaboration material.
 
-- Adopt an IaC approach for deploying, managing, governing and supporting cloud resources.
+- Adopt an IaC approach for deploying, managing, governing, and supporting cloud resources.
 
 ## Branch strategy
 
@@ -123,7 +123,7 @@ Development lifecycle strategy provides key design considerations and recommenda
 
 - When you connect Azure DevOps or GitHub to Azure via service connections or GitHub secrets, make sure you always define the scope so they can access only required resources.
 
-- Use Key Vault secrets to avoid hard-coding sensitive information such as credentials (virtual machine´s user passwords), certificates or keys. Then use secrets as variables in your build and release jobs.
+- Use Key Vault secrets to avoid hard-coding sensitive information such as credentials (virtual machine´s user passwords), certificates, or keys. Then use secrets as variables in your build and release jobs.
 
 ## Deployment strategy
 
@@ -138,7 +138,7 @@ Development lifecycle strategy provides key design considerations and recommenda
   - Staging
   - Production
 
-- Consider using IaC as part of your strategy to validate and confirm changes pre-deployment.
+- Consider using IaC as part of your strategy to validate and confirm changes predeployment.
   - [ARM Templates what-if](/azure/azure-resource-manager/templates/deploy-what-if?tabs=azure-powershell)
   - [Bicep what-if](/azure/azure-resource-manager/bicep/deploy-what-if?tabs=azure-powershell%2cCLI)
   - [Terraform plan](https://www.terraform.io/cli/commands/plan)
@@ -153,16 +153,16 @@ Development lifecycle strategy provides key design considerations and recommenda
   - Diagnostic resource health
   - Security
 
-- Include IaC pre-deployment checks so you can preview changes and see details on whether a resource has been created, modified, or deleted.
+- Include IaC predeployment checks so you can preview changes and see details on whether a resource is created, modified, or deleted.
 
 ## Rollback strategy
 
 ### Design considerations
 
 - Consider creating a rollback plan. Rolling back a deployment involves reverting the deployment to a known good state and provides a crucial ability to recover from a failed deployment.
 
-- Consider using [undo changes](/azure/devops/repos/git/undo) in Git if you need to revert changes in a commit, discard changes or reset a branch to a previous state.
+- Consider using [undo changes](/azure/devops/repos/git/undo) in Git if you need to revert changes in a commit, discard changes, or reset a branch to a previous state.
 
 ### Design recommendations
 
-- Adopt the use of undo changes in Git when you need to revert changes to committed files, discard uncommitted changes or reset a branch to a previous state.
+- Adopt the use of undo changes in Git when you need to revert changes to committed files, discard uncommitted changes, or reset a branch to a previous state.

docs/ready/landing-zone/index.md

@@ -59,7 +59,7 @@ You should use the Azure landing zone portal accelerator if you plan to manage y
 
 ### Application landing zone accelerators
 
-[Application landing zone accelerators](/azure/architecture/landing-zones/landing-zone-deploy#application) help you deploy application landing zones. Use the list of available application landing zone accelerators in the [Azure Architecture Center](/azure/architecture/landing-zones/landing-zone-deploy#application) and deploy the accelerator that matches your scenario.
+Application landing zone accelerators help you deploy application landing zones. Use the list of available application landing zone accelerators in the [Azure Architecture Center](/azure/architecture/landing-zones/landing-zone-deploy#application) and deploy the accelerator that matches your scenario.
 
 <!-- markdownlint-disable MD034 -->
 

docs/scenarios/cloud-scale-analytics/architectures/what-is-data-mesh.md

@@ -1,9 +1,9 @@
 ---
 title: What is a data mesh?
 description: Learn about data mesh in Azure.
-author: simonlid
-ms.author: simonlid
-ms.date: 03/12/2023
+author: mboswell
+ms.author: mboswell
+ms.date: 09/30/2024
 ms.topic: conceptual
 ms.custom: e2e-data-management, think-tank
 ---
@@ -20,8 +20,6 @@ However, as business changes and generates more diverse data, data warehousing s
 
 In recent years, many organizations successfully use modern architectural and analytical patterns that combine data warehousing technologies and more recent big data technologies.
 
-:::image type="content" source="../media/azure-analytics-end-to-end.png" alt-text="Diagram of architecture." lightbox="../media/azure-analytics-end-to-end.png":::
-
 However, some organizations encounter issues when deploying analytical solutions that use analytical patterns. These solutions are commonly still implemented as monolithic solutions, where a single team is the platform provider and the team is doing data integration. Smaller organizations and organizations that have a high degree of centralization from a team setup perspective can use a single team. However, a larger organization using only a single team often creates a bottleneck. This bottleneck causes a huge backlog, which results in parts of an organization waiting for data integration services and analytical solutions.
 
 This pattern becomes more common as organizations adopt modern data science solutions. Many modern data science solutions require more data than traditional business intelligence solutions did in the past.
@@ -30,7 +28,7 @@ The recent switch to using microservices as an application development pattern i
 
 A single team handling all data ingestion on a single platform in a large organization can also be problematic. One team rarely has experts for every data source. Most organizations are decentralized and distributed from a business perspective. Different business units and departments handle different parts of the business operation, so data experts are typically spread out across various sectors.
 
-A new architectural pattern called data mesh was introduced recently to solve these problems. Data mesh's goal is to let distributed teams work with and share information in a decentralized and agile manner.
+A pattern called data mesh was introduced to solve these problems. Data mesh's goal is to let distributed teams work with and share information in a decentralized and agile manner.
 
 Data mesh is a technical pattern that also requires organizational change. The benefits of a data mesh approach are achieved by implementing multi-disciplinary teams that publish and consume data products.
 
@@ -81,7 +79,7 @@ You can successfully implement your self-serve platform by adopting the practice
 
 ## Federated governance
 
-When you adopt a self-serve distributed data platform, you must place an increased emphasis on governance. Lack of governance leads to silos and data duplication across your data domains. Federate your governance, as people who understand the governance need exist within your domain aligned teams and amongst data owners.
+When you adopt a self-serve distributed data platform, you must place an increased emphasis on governance. Lack of governance leads to silos and data duplication across your data domains. Federate your governance, as people who understand the governance need exist within your domain aligned teams and among data owners.
 
 To create your federated governance, implement automated policies around both platform and data needs. Use a high degree of automation for testing and monitoring. Adopt a code-first implementation strategy to handle standards, policies, data products, and platform deployment as code.
 
@@ -93,6 +91,7 @@ Data mesh can be an effective way to implement enterprise data platforms, but it
 
 When using data mesh, take special care when implementing your governance so you don't create silos. Always keep product thinking for data at the core of your implementation to ensure success.
 
-## Next Steps
+## Next steps
 
-[Data domains](data-domains.md)
+> [!div class="nextstepaction"]
+> [Data domains](data-domains.md)