Merge pull request #50386 from lootle1/MR103

v-ccolin · web-flow · commit 8d62adbde212 · 2025-05-21T16:01:50.000+01:00
Technical Review 1044282: Innovate applications by using Azure cloud …
diff --git a/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/1-introduction.yml b/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/1-introduction.yml
@@ -3,7 +3,7 @@ uid: learn.innovate-applications-azure-cloud-technologies.1-introduction
 metadata:
   title: Introduction
   description: Introduction
-  ms.date: 04/14/2023
+  ms.date: 05/12/2025
   author: Zimmergren
   ms.author: tozimmergren
   ms.topic: unit
diff --git a/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/2-innovation-lifecycle.yml b/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/2-innovation-lifecycle.yml
@@ -3,7 +3,7 @@ uid: learn.innovate-applications-azure-cloud-technologies.2-innovation-lifecycle
 metadata:
   title: Follow the innovation lifecycle
   description: The build, measure, and learn phases of the innovation lifecycle.
-  ms.date: 04/14/2023
+  ms.date: 05/12/2025
   author: Zimmergren
   ms.author: tozimmergren
   ms.topic: unit
diff --git a/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/3-azure-technologies-build-process.yml b/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/3-azure-technologies-build-process.yml
@@ -3,7 +3,7 @@ uid: learn.innovate-applications-azure-cloud-technologies.3-azure-technologies-b
 metadata:
   title: Azure technologies for the build process
   description: Azure technologies and services that can help during the build process of the innovation lifecycle.
-  ms.date: 04/14/2023
+  ms.date: 05/12/2025
   author: Zimmergren
   ms.author: tozimmergren
   ms.topic: unit
diff --git a/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/4-infuse-application-artificial-intelligence.yml b/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/4-infuse-application-artificial-intelligence.yml
@@ -3,7 +3,7 @@ uid: learn.innovate-applications-azure-cloud-technologies.4-infuse-application-a
 metadata:
   title: Infuse your applications with AI
   description: Using Azure services to enrich applications with Machine Learning and AI.
-  ms.date: 04/14/2023
+  ms.date: 05/12/2025
   author: Zimmergren
   ms.author: tozimmergren
   ms.topic: unit
diff --git a/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/5-azure-technologies-measure-process.yml b/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/5-azure-technologies-measure-process.yml
@@ -3,7 +3,7 @@ uid: learn.innovate-applications-azure-cloud-technologies.5-azure-technologies-m
 metadata:
   title: Azure technologies for measuring business impact
   description: Using Azure Application Insights to support the measure step of the innovation lifecycle
-  ms.date: 04/14/2023
+  ms.date: 05/12/2025
   author: Zimmergren
   ms.author: tozimmergren
   ms.topic: unit
diff --git a/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/6-manage-workload-operations.yml b/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/6-manage-workload-operations.yml
@@ -3,7 +3,7 @@ uid: learn.innovate-applications-azure-cloud-technologies.6-azure-technologies-l
 metadata:
   title: Azure technologies for the learn process
   description: Data democratization and its role in the innovation process
-  ms.date: 04/14/2023
+  ms.date: 05/12/2025
   author: Zimmergren
   ms.author: tozimmergren
   ms.topic: unit
diff --git a/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/7-knowledge-check.yml b/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/7-knowledge-check.yml
@@ -4,7 +4,7 @@ title: Module assessment
 metadata:
   title: Module assessment
   description: Knowledge check
-  ms.date: 04/14/2023
+  ms.date: 05/12/2025
   author: Zimmergren
   ms.author: tozimmergren
   ms.topic: unit
diff --git a/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/8-summary.yml b/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/8-summary.yml
@@ -3,7 +3,7 @@ uid: learn.innovate-applications-azure-cloud-technologies.8-summary
 metadata:
   title: Summary
   description: Summary
-  ms.date: 04/14/2023
+  ms.date: 05/12/2025
   author: Zimmergren
   ms.author: tozimmergren
   ms.topic: unit
diff --git a/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/includes/2-innovation-lifecycle.md b/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/includes/2-innovation-lifecycle.md
@@ -3,7 +3,7 @@ Tailwind Traders has questions about innovation that affect many other organizat
 - How do we increase the rate of change without affecting the running business?
 - How do we decide where to innovate and what changes to implement to maximize the business return of those innovations?
 
-The answer to both questions is: Tailwind Traders needs to embrace change as part of its organizational culture. One reason why change-averse organizations often have change-related outages is that those changes are too large and impactful. The changes are hard to test in controlled and realistic environments.
+The answer to both questions, Tailwind Traders needs to embrace change as part of its organizational culture. One reason why change-averse organizations often have change-related outages is that those changes are too large and impactful. The changes are hard to test in controlled and realistic environments.
 
 If processes are established to introduce changes frequently, those changes are smaller in size and risk. However, this process doesn't just involve adopting certain tools or technologies. It requires a culture that fosters change and accepts failures.
 
diff --git a/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/includes/3-azure-technologies-build-process.md b/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/includes/3-azure-technologies-build-process.md
@@ -8,7 +8,7 @@ After you've started the build phase to validate your innovation hypothesis, the
 - **Quick delivery of software features**: DevOps processes and tools embrace the concept of failing fast. Building MVPs or prototypes to quickly validate whether the feature on which you're working goes in the right direction is core to the concept of DevOps.
 - **Reliable delivery of software features**: Change-averse organizations often associate quick changes with downtime. However, DevOps promises exactly the opposite: a quick change rate and a high level of reliability. This reliability is made possible by integrating testing in early stages of the development cycle, in a process called "shift to the left."
 
-  If the development of a feature across time is seen as a line from left to right. Then, a legacy development process would perform user validation and quality control at the end of the development cycle. At the "right" end of that line. DevOps advises you to test and validate as early as possible, at the "left" of that time line.
+  If the development of a feature across time is seen as a line from left to right, then a legacy development process would perform user validation and quality control at the end of the development cycle. This is at the "right" end of that line. DevOps advises you to test and validate as early as possible, at the "left" of that time line.
 
 DevOps embodies the same core concepts of a healthy innovation culture. Adopting its methodology is key to get to an agile innovation cycle.
 
@@ -18,7 +18,7 @@ Modularity is a well-known technique to reduce complexity in architecting comple
 
 If the system is modular, you can separate it into smaller subsystems that interact with each other via well-defined interfaces. Introducing changes in one of these subsystems is easier, because as long as its interface with the other modules stays constant, the overall system continues working.
 
-Microservices architectures are application patterns that exploit modularity. Applications are subdivided into separate, small components that can be developed independently from each other, potentially even using different programming languages. Each component, or microservice, can operate on its own. You can scale it as required, you can troubleshoot it as a single unit, you can modify it independently from the other microservices.
+Microservices architectures are application patterns that exploit modularity. Applications are subdivided into separate, small components that can be developed independently from each other, potentially even using different programming languages. Each component, or microservice, can operate on its own. You can scale it as required, you can troubleshoot it as a single unit, and you can modify it independently from the other microservices.
 
 A question that organizations often ask is what to do if an application is monolithic. Should the organization redesign the application into a microservices architecture before introducing innovation, or can the innovation and redesign processes run in parallel? There's no single answer to this question. It depends on the complexity and business relevance of the application under consideration.
 
@@ -32,7 +32,7 @@ The projects are to interact with each other, guided by the business value of in
 
 The technology of containerization isn't exclusive to microservices architectures, but the concepts work together. Containers are a way to encapsulate application code and its dependencies so that they can be deployed effortlessly in any platform.
 
-Traditional application deployments require the organization to install software first, such as the application runtime, programming libraries, or external components. This approach often results in the "it works on my machine" problem: it's difficult to replicate the same environment across development, test, staging, and production. Small differences in the way that the application dependencies are installed can cause the application to work fine while being tested, but fail when it's deployed into production.
+Traditional application deployments require the organization to install software first, such as the application runtime, programming libraries, or external components. This approach often results in the "it works on my machine" problem since it's difficult to replicate the same environment across development, test, staging, and production. Small differences in the way that the application dependencies are installed can cause the application to work fine while being tested but fail when it's deployed into production.
 
 Containers change the rules of the game. The application dependencies are packed along with the application code in an autonomous deployment unit called the container image. Whether the application container is deployed on a developer's laptop or in a production cluster with hundreds of nodes, the dependency handling is the same. The container works exactly the same way, so application testing is more reliable and trustworthy.
 
@@ -52,7 +52,7 @@ Running Kubernetes in Azure is easy. [Azure Kubernetes Service](/azure/aks/intro
 
 ## Azure App Service
 
-[Azure App Service](/azure/app-service/overview?azure-portal=true) is a platform where organizations can run their web-based workloads without having to manage any orchestrator or underlying operating system. The only requirement is uploading the application code to the service through one of many available deployment methods. Azure does the rest: scaling the application in and out, patching and maintaining the underlying virtual machines, and much more, without requiring the learning curve of Kubernetes.
+[Azure App Service](/azure/app-service/overview?azure-portal=true) is a platform where organizations can run their web-based workloads without having to manage any orchestrator or underlying operating system. The only requirement is uploading the application code to the service through one of many available deployment methods. Azure does the rest to include scaling the application in and out, patching and maintaining the underlying virtual machines, and much more. All this without requiring the learning curve of Kubernetes.
 
 Azure App Service supports container-based workloads, so you can upload your container image instead of the application code. It also supports Linux and Windows workloads and many different application runtimes.
 
diff --git a/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/includes/4-infuse-application-artificial-intelligence.md b/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/includes/4-infuse-application-artificial-intelligence.md
@@ -4,7 +4,7 @@ In this unit, you learn the importance of machine learning and AI technologies i
 
 Machine learning and AI are great assets for improving interaction with your customers and partners. Tailwind Traders is evaluating these application features as a way to enhance the user experience and increase business value.
 
-In addition to transforming its main e-commerce applications into a microservices architecture, the company wants to introduce new functionality to enhance customer experience. Currently, they have no staff with data-science skills. New staff will be hired in the future, but in the meantime, the company should identify quick wins that can help in improving the competitiveness of its web shop.
+In addition to transforming its main e-commerce applications into a microservices architecture, the company wants to introduce new functionality to enhance customer experience. Currently, they have no staff with data-science skills. New staff will be hired in the future, but in the meantime the company should identify quick wins that can help in improving the competitiveness of its web shop.
 
 Tailwind Traders is evaluating four possibilities:
 
@@ -23,11 +23,11 @@ Azure offers tools and services that can help organizations build machine learni
 
 ### Azure AI services
 
-[Azure AI services](/azure/ai-services/what-are-ai-services) contains prebuilt models that don't require machine-learning expertise to introduce AI functionality to an application. Azure AI services encompasses many areas, such as vision, speech, language, decision, and search. It's easy to use, so organizations can use the power of AI without extensive machine-learning skills.
+[Azure AI services](/azure/ai-services/what-are-ai-services) contains prebuilt models that don't require machine-learning expertise to introduce AI functionality to an application. Azure AI services encompass many areas, such as vision, speech, language, decision, and search. It's easy to use, so organizations can use the power of AI without extensive machine-learning skills.
 
 Tailwind Traders sees a high potential in Azure AI services, because its data-science department isn't fully operational. The company is evaluating these features to innovate the e-commerce application:
 
-- **Personalizer**: Organizations can use this feature to learn which users prefer which products, and to make fine-tuned, individual recommendations. Some customers prefer products with quick delivery, whereas other customers prefer products on sale. Personalizer uses a type of machine-learning algorithm called *reinforcement learning*, which doesn't require huge amounts of data to be trained. Tailwind Traders is interested in Personalizer, because it doesn't have this type of data yet.
+- **Personalizer**: Organizations can use this feature to learn which users prefer which products and to make fine-tuned, individual recommendations. Some customers prefer products with quick delivery, whereas other customers prefer products on sale. Personalizer uses a type of machine-learning algorithm called *reinforcement learning*, which doesn't require huge amounts of data to be trained. Tailwind Traders is interested in Personalizer because it doesn't have this type of data yet.
 - **Text Analytics**: Many users write product reviews. Organizations can analyze reviews to find customers who express negative sentiments. Focusing on these customers can reduce customer churn and increase loyalty.
 - **Translator**: Product reviews can be an effective sales tool, but they're useful only to customers who understand the language they're written in. Using real-time translation services would allow Tailwind Traders to show product reviews to any user regardless of their native language.
 
diff --git a/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/includes/5-azure-technologies-measure-process.md b/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/includes/5-azure-technologies-measure-process.md
@@ -8,7 +8,7 @@ However, the way in which features are released to application users can help to
 
 - Controlled deployments with *feature flags*, *feature rings*, and *canary deployments* allow you to release a feature to a limited set of users to prevent disrupting the experience of the whole customer base. Additionally, you can directly compare the performance of the customers with and without the feature to each other.
 - *Portal options* for users to decide if they want to be exposed to new functionality puts the users in control of their own experience. The fact that many users opt for a new feature might already be a confirmation that the previous functionality had room for improvement. If customers that opt for the new feature go back to the previous experience, it might be an indicator that the deployed MVP is missing the mark.
-- *Customer surveys* are a powerful feedback mechanism if they're implemented correctly. Customers provide information about their satisfaction if it's simple to give. One-click "traffic light" satisfaction surveys or single questions about new functionality might provide insights to help in evaluating whether the innovation hypothesis was correct. In general, only a few users answer longer surveys, and take the time to fill them in thoroughly and truthfully.
+- *Customer surveys* are a powerful feedback mechanism if they're implemented correctly. Customers provide information about their satisfaction if it's simple to give. One-click "traffic light" satisfaction surveys or single questions about new functionality might provide insights to help in evaluating whether the innovation hypothesis was correct. In general, only a few users answer longer surveys and take the time to fill them in thoroughly and truthfully.
 
 ## Understanding your application
 
@@ -30,17 +30,17 @@ Notifications typically report that there might be a problem without context abo
 
 After you formulate a hypothesis with the data provided by Azure Application Insights, you can analyze telemetry to measure whether the situation is now better or worse. You can embed custom business events in the application so that telemetry data contains additional information that helps in the measure process.
 
-[Funnels](/azure/azure-monitor/app/usage-funnels?azure-portal=true) can be an insightful tool. With funnels, you can predefine the *flows* that you expect users to follow when they use the application. Then you can monitor which patterns users follow, and identify problems in the applications if users behave in unexpected ways.
+[Funnels](/azure/azure-monitor/app/usage?tabs=aspnetcore&branch=main#funnels---discover-how-customers-use-your-application) can be an insightful tool. With funnels, you can predefine the *flows* that you expect users to follow when they use the application. Then you can monitor which patterns users follow, and identify problems in the applications if users behave in unexpected ways.
 
 ### Retain users
 
-The Application Insights [retention tool](/azure/azure-monitor/app/usage-retention#the-retention-tool?azure-portal=true) offers specific functionality around user churn. It contains valuable learning data when combined with business events. For example, understanding which actions that customers who left the application unexpectedly took, allows you to formulate hypotheses with maximum business impact.
+The Application Insights [retention tool](/azure/azure-monitor/app/usage?tabs=aspnetcore&branch=main#user-retention-analysis) offers specific functionality around user churn. It contains valuable learning data when combined with business events. For example, understanding which actions customers who left the application unexpectedly took, allows you to formulate hypotheses with maximum business impact.
 
 For example, if most users who abandoned your website did so from the payment method page, you'd suspect a business problem there. Maybe the payment options are insufficient or not clearly displayed, or another problem is preventing users from moving forward in their shopping process.
 
 ### Impact analysis
 
-[Impact analysis](/azure/azure-monitor/app/usage-impact?azure-portal=true) is a feature in Azure Application Insights that correlates technical aspects of the application to tangible business metrics.
+[Impact analysis](/azure/azure-monitor/app/usage?tabs=aspnetcore&branch=main#impact-analysis---discover-how-different-properties-influence-conversion-ratess) is a feature in Azure Application Insights that correlates technical aspects of the application to tangible business metrics.
 
 For example, how fast should the product page load so that most users continue with their shopping process? With impact analysis, you can show the relationship between page load time and the rate of users who purchase the product shown. This information can help you to validate or reject an innovation hypothesis, and to convert business requirements into technical specifications.
 
diff --git a/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/includes/6-azure-technologies-learn-process.md b/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/includes/6-azure-technologies-learn-process.md
@@ -69,7 +69,7 @@ The next step after data classification is ensuring that each data category is p
 - **Data auditing**: Many regulatory compliance standards demand evidence of data protection mechanisms by documenting who has done certain operations and accessed certain data. As described in [Auditing for Azure SQL Database and Azure Synapse Analytics](/azure/azure-sql/database/auditing-overview?azure-portal=true), data auditing in Azure contemplates three aspects of auditing:
   - *Retain* an audit trail of selected events, where you can define categories of data actions to be audited.
   - *Report* on database activity, optionally with preconfigured reports and dashboards to get started quickly.
-  - *Analyze* reports to uncover suspicious events, unusual activity, and trends
+  - *Analyze* reports to uncover suspicious events, unusual activity, and trends.
 
 ## Growth mindset
 
@@ -83,4 +83,4 @@ A growth mindset is fundamental at this stage. Think of hypotheses proven wrong
 
 ## Where to look next
 
-We further discuss many of the concepts in this unit in the Cloud Adoption Framework documentation about [data democratization](/azure/cloud-adoption-framework/innovate/best-practices/data?azure-portal=true).
+We further discuss many of the concepts in this unit in the Cloud Adoption Framework documentation about [data democratization](/azure/cloud-adoption-framework/innovate/best-practices/data?azure-portal=true).
diff --git a/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/includes/8-summary.md b/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/includes/8-summary.md
diff --git a/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/index.yml b/learn-pr/azure/innovate-applications-with-azure-cloud-technologies/index.yml
