Merge pull request #51200 from v-thpra/azure-triage-fix-1058619

JamesJBarnett · web-flow · commit f9d8f1885da0 · 2025-07-07T10:46:39.000-07:00
Technical Review 1058619: Introduction to cloud-native apps on Azure
diff --git a/learn-pr/azure/introduction-to-cloud-native-apps/1-introduction.yml b/learn-pr/azure/introduction-to-cloud-native-apps/1-introduction.yml
@@ -4,9 +4,9 @@ title: Introduction
 metadata:
   title: Introduction
   description: Introduction to cloud-native apps
-  ms.date: 03/02/2023
-  author: tomreidnz
-  ms.author: jasdeb
+  ms.date: 07/02/2025
+  author: carols
+  ms.author: carols
   ms.topic: unit
 durationInMinutes: 2
 content: |
diff --git a/learn-pr/azure/introduction-to-cloud-native-apps/2-what-are-cloud-native-apps.yml b/learn-pr/azure/introduction-to-cloud-native-apps/2-what-are-cloud-native-apps.yml
@@ -4,9 +4,9 @@ title: What are cloud-native apps?
 metadata:
   title: What are cloud-native apps?
   description: An overview of cloud-native apps
-  ms.date: 03/02/2023
-  author: tomreidnz
-  ms.author: jasdeb
+  ms.date: 07/02/2025
+  author: carols
+  ms.author: carols
   ms.topic: unit
 durationInMinutes: 5
 content: |
diff --git a/learn-pr/azure/introduction-to-cloud-native-apps/3-containers-cloud-native.yml b/learn-pr/azure/introduction-to-cloud-native-apps/3-containers-cloud-native.yml
@@ -4,9 +4,9 @@ title: Using containers with cloud-native apps
 metadata:
   title: Using containers with cloud-native apps
   description: An overview of containers and kubernetes
-  ms.date: 03/02/2023
-  author: tomreidnz
-  ms.author: jasdeb
+  ms.date: 07/02/2025
+  author: carols
+  ms.author: carols
   ms.topic: unit
 durationInMinutes: 5
 content: |
diff --git a/learn-pr/azure/introduction-to-cloud-native-apps/4-design-cloud-native-apps.yml b/learn-pr/azure/introduction-to-cloud-native-apps/4-design-cloud-native-apps.yml
@@ -4,9 +4,9 @@ title: Designing a cloud-native app
 metadata:
   title: Designing a cloud-native app
   description: A high-level explanation of the parts of cloud native apps
-  ms.date: 03/02/2023
-  author: tomreidnz
-  ms.author: jasdeb
+  ms.date: 07/02/2025
+  author: carols
+  ms.author: carols
   ms.topic: unit
 durationInMinutes: 6
 content: |
diff --git a/learn-pr/azure/introduction-to-cloud-native-apps/5-when-to-use-cloud-native-apps.yml b/learn-pr/azure/introduction-to-cloud-native-apps/5-when-to-use-cloud-native-apps.yml
@@ -4,9 +4,9 @@ title: When to use cloud-native apps
 metadata:
   title: When to use cloud-native apps
   description: We examine where cloud-native apps would be useful, and where it might not be the right choice
-  ms.date: 03/02/2023
-  author: tomreidnz
-  ms.author: jasdeb
+  ms.date: 07/02/2025
+  author: carols
+  ms.author: carols
   ms.topic: unit
 durationInMinutes: 4
 content: |
diff --git a/learn-pr/azure/introduction-to-cloud-native-apps/6-knowledge-check.yml b/learn-pr/azure/introduction-to-cloud-native-apps/6-knowledge-check.yml
@@ -4,9 +4,9 @@ title: Module assessment
 metadata:
   title: Module assessment
   description: Multiple-choice questions
-  ms.date: 03/02/2023
-  author: tomreidnz
-  ms.author: jasdeb
+  ms.date: 07/02/2025
+  author: carols
+  ms.author: carols
   ms.topic: unit
   module_assessment: true
 durationInMinutes: 3
@@ -19,12 +19,12 @@ quiz:
     - content: "A single codebase where all the different functionalities reside."
       isCorrect: false
       explanation: "Incorrect. A single codebase would indicate a monolithic approach. A cloud-native approach separates different functionality."
-    - content: "Architectural modularity, using pre-built cloud services and container technologies where they're best suited."
+    - content: "Architectural modularity, using prebuilt cloud services and container technologies where they're best suited."
       isCorrect: true
-      explanation: "Correct. A cloud-native architecture focuses on having individual, separated components that form different services. CNAs are built to use cloud-based services to handle aspects like security where appropriate."
+      explanation: "Correct. Cloud-native architectures (CNAs) focus on having individual, separated components that form different services. CNAs are built to use cloud-based services to handle aspects like security where appropriate."
     - content: "A hybrid-cloud approach."
       isCorrect: false
-      explanation: "Incorrect. While a hybrid-cloud approach may be part of some cloud-native architectures, not all cloud-native architectures use a hybrid cloud approach."
+      explanation: "Incorrect. While a hybrid-cloud approach can be part of some cloud-native architectures, not all cloud-native architectures use a hybrid cloud approach."
     - content: "Smart fridges."
       isCorrect: false
       explanation: "Incorrect. Smart fridges are our scenario, not all cloud-native apps focus on smart fridges."
@@ -47,12 +47,12 @@ quiz:
     - content: "A cloud-native approach allows rapid incorporation of user feedback."
       isCorrect: false
       explanation: "Incorrect. While a cloud-native approach can provide rapid incorporation of user feedback, there are other ways cloud-native apps help to create business value."
-    - content: "Cloud services have built in tools and integrations for automation, such as continuous integration (CI) and continuous deployment (CD) pipelines. Therefore, cloud-native apps are more likely to have robust DevOps procedures, which can decrease costs and increase reliability."
+    - content: "Cloud services provide built-in tools and integrations for automation, such as continuous integration (CI) and continuous deployment (CD) pipelines. Therefore, cloud-native apps are more likely to have robust DevOps procedures, which can decrease costs and increase reliability."
       isCorrect: false
       explanation: "Incorrect. While automation is a benefit of cloud native processes, there are other ways cloud-native apps help to create business value"
     - content: "A Cloud Native architecture allows individual services to be updated and deployed without downtime for other services."
       isCorrect: false
       explanation: "Incorrect. While there's significant business value from being able to update a service with no downtime for other services, there are other ways cloud-native apps help to create business value"
-    - content: "All of the above."
+    - content: "All of these answers are true."
       isCorrect: true
       explanation: "Correct. Rapid incorporation of user feedback increases business agility for constant improvement, automation can decrease costs and increase reliability, and individual services being able to update a service with no downtime for other services all provide real business value."
diff --git a/learn-pr/azure/introduction-to-cloud-native-apps/7-summary.yml b/learn-pr/azure/introduction-to-cloud-native-apps/7-summary.yml
@@ -4,9 +4,9 @@ title: Summary
 metadata:
   title: Summary
   description: Summary
-  ms.date: 03/02/2023
-  author: tomreidnz
-  ms.author: jasdeb
+  ms.date: 07/02/2025
+  author: carols
+  ms.author: carols
   ms.topic: unit
 durationInMinutes: 2
 content: |
diff --git a/learn-pr/azure/introduction-to-cloud-native-apps/includes/1-introduction.md b/learn-pr/azure/introduction-to-cloud-native-apps/includes/1-introduction.md
@@ -4,6 +4,6 @@ Many cloud architects opt for Open-Source Software (OSS) like Kubernetes and Doc
 
 ## Scenario: Smart refrigerators, smarter service, at scale
 
-Suppose you work for Adatum Corporation, a manufacturer of home appliances, where you lead a small development team and you've been tasked with building an app for smart refrigerators.
+Suppose you work for Adatum Corporation, a manufacturer of home appliances. You lead a small development team and you're tasked with building an app for smart refrigerators.
 
-We could, for example, start with creating a small inventory management app for the refrigerators, so businesses can know what needs to be restocked, or potentially, have items reordered automatically. It's the nature of cloud-native apps to have loosely coupled functionality, so we can be more agile in our design and avoid having to predict future requirements. Rather, we can extend the app if it becomes necessary. Later, we can add functionality to the app, such as connecting to refrigerator telemetry and onboard sensors.
+We could, for example, start with creating a small inventory management app for the refrigerators, so businesses can know what needs to be restocked, or potentially, have items reordered automatically. It's the nature of cloud-native apps to contain loosely coupled functionality, so we can be more agile in our design and avoid having to predict future requirements. Rather, we can extend the app if it becomes necessary. Later, we can add functionality to the app, such as connecting to refrigerator telemetry and onboard sensors.
diff --git a/learn-pr/azure/introduction-to-cloud-native-apps/includes/2-what-are-cloud-native-apps.md b/learn-pr/azure/introduction-to-cloud-native-apps/includes/2-what-are-cloud-native-apps.md
@@ -5,7 +5,7 @@ The cloud-native approach allows you to build cloud-based applications where you
 
 Additionally, cloud-native apps are modular in nature. You choose the cloud services and technologies, and loosely couple them together as shown in the diagram. Cloud-native apps often employ another pattern, called **Microservices.** Notice how each service has its own technology stack, independent of what other services use, meaning you choose the technologies that suit each individual service, rather than a one-size-fits-all solution.
 
-With Cloud Native, we're using many pre-built types of services or services with pre-built infrastructure. So we can use scaling from Kubernetes or Azure Function Apps, and geo-redundant data storage from Cosmos DB or Hyperscale for PostgreSQL.
+With Cloud Native, we're using many prebuilt types of services or services with prebuilt infrastructure. So we can use scaling from Kubernetes or Azure Function Apps, and geo-redundant data storage from Cosmos DB or Hyperscale for PostgreSQL.
 
 :::column-end:::
 :::column:::
@@ -24,9 +24,9 @@ Further, with different components loosely coupled together to create an applica
 :::row:::
 :::column span="3":::
 
-Most cloud-native services support a wide range of technologies. Kubernetes supports multiple client OSs and any tech stack, such as .NET, Node, Ruby, and Java. There are vast options for databases that can be connected using any major programming language.
+Most cloud-native services support a wide range of technologies. Kubernetes supports multiple client operating systems (OSs) and any tech stack, such as .NET, Node, Ruby, and Java. There are vast options for databases that can be connected using any major programming language.
 
-You can connect a backend to your relational database of choice for one service, while also using a NoSQL database and a pre-built analytics service when it’s a better fit for another service. You can do it all quickly and simply, within the same overall cloud application.
+You can connect a backend to your relational database of choice for one service, while also using a NoSQL database and a prebuilt analytics service when it’s a better fit for another service. You can do it all quickly and simply, within the same overall cloud application.
 
 :::column-end:::
 :::column:::
diff --git a/learn-pr/azure/introduction-to-cloud-native-apps/includes/3-containers-cloud-native.md b/learn-pr/azure/introduction-to-cloud-native-apps/includes/3-containers-cloud-native.md
@@ -26,7 +26,7 @@ Containers are easy to use with cloud services. They ensure that, once tested, y
 
 Kubernetes, often abbreviated as K8s, is a technology that manages multiple containers for you. You can connect containers so your database can talk to a backend, scale resources, and automate application deployment, backups, and maintenance.
 
-One of the key benefits of Kubernetes is the ability to restore applications to the exact instance that has been tested and saved, otherwise known as **self-healing**. As containers can be saved and replicated, Kubernetes can check on the health of a container and replace it with an original copy if necessary.
+One of the key benefits of Kubernetes is the ability to restore applications to the exact instance that was tested and saved, otherwise known as **self-healing**. As containers can be saved and replicated, Kubernetes can check on the health of a container and replace it with an original copy if necessary.
 
 Kubernetes can also automatically increase or decrease the number of containers if demand changes. If traffic to a container is high, Kubernetes can load balance and distribute the network traffic so that the deployment is stable.
 
@@ -38,6 +38,6 @@ Kubernetes can also automatically increase or decrease the number of containers
 :::column-end:::
 :::row-end:::
 
-Additionally, one of the main benefits of using a Kubernetes service is simplified security configuration management. Many have built in authentication services, allowing the services to provide compliance offerings for most countries/regions and industries.
+Additionally, one of the main benefits of using a Kubernetes service is simplified security configuration management. Many have built-in authentication services, allowing the services to provide compliance offerings for most countries/regions and industries.
 
-Further, when a component is updated, you can automate Kubernetes to create new containers for your deployment, remove existing containers, and adopt all their resources to the new containers. Kubernetes services, such as AKS, simplify container management and can provide massive savings in development time, cost, and security obligations. Continuous integration and continuous delivery (CI/CD), allow Kubernetes services to optimize development pipelines and application deployment.
+Further, when a component is updated, you can automate Kubernetes to create new containers for your deployment, remove existing containers, and adopt all their resources to the new containers. Kubernetes services, such as Azure Kubernetes Service (AKS), simplify container management and can provide massive savings in development time, cost, and security obligations. Continuous integration and continuous delivery (CI/CD), allow Kubernetes services to optimize development pipelines and application deployment.
diff --git a/learn-pr/azure/introduction-to-cloud-native-apps/includes/4-design-cloud-native-apps.md b/learn-pr/azure/introduction-to-cloud-native-apps/includes/4-design-cloud-native-apps.md
@@ -1,10 +1,10 @@
-Because cloud-native apps are made up of the components of your choice, you can easily architect a solution that uses technologies you're comfortable with. For example, if Python better suits your data analytics service, but your email service is more suited to using a pre-built solution, the architectural modularity of cloud-native apps significantly simplifies implementation. This modularity even extends across different cloud providers.
+Because cloud-native apps are made up of the components of your choice, you can easily architect a solution that uses technologies you're comfortable with. For example, if Python better suits your data analytics service, but your email service is more suited to using a prebuilt solution, the architectural modularity of cloud-native apps significantly simplifies implementation. This modularity even extends across different cloud providers.
 
 For example, many cloud services, such as Azure Database for MySQL, allow you to develop using the open-source versions of technologies that you’re used to, but have Azure take care of administration and deployment responsibilities for you.
 
 ### Architecting a cloud-native solution for Adatum
 
-In our scenario, we can architect a solution that’s easy for a small team to develop but also scales safely to thousands of devices. Cloud functionality eliminates many development issues arising from a need to connect to large numbers of devices and process data on demand. By using cloud infrastructure, pre-built services can be easily configured to communicate with each other and autoscale as needed.
+In our scenario, we can architect a solution that’s easy for a small team to develop but also scales safely to thousands of devices. Cloud functionality eliminates many development issues arising from a need to connect to large numbers of devices and process data on demand. By using cloud infrastructure, prebuilt services can be easily configured to communicate with each other and autoscale as needed.
 
 Later, if necessary, the solution can grow to accommodate new or updated products. In our scenario, if a hotel chain ordering thousands of refrigerators needs extra functionality, you can create an extra service with no downtime for existing customers.
 
@@ -32,9 +32,9 @@ This solution is easily connected to your database of choice, allowing a scalabl
 
 Smart devices offer a wealth of connectivity and data options. Advancements in the IoT field offer cost-effective options for gathering data and streaming it to the cloud. IoT cloud services for smart devices are easy to connect, allowing you to stream telemetry data such as refrigerator temperatures, power consumption, and water quality.
 
-Developers can use cloud-services, such as IoT Hub and Stream Analytics, to develop cloud-native apps with IoT integration. Since much of the groundwork has been done for you, development time can be decreased significantly.
+Developers can use cloud-services, such as IoT Hub and Stream Analytics, to develop cloud-native apps with IoT integration. Since much of the groundwork is done for you, development time can be decreased significantly.
 
-Because of the loosely coupled nature of cloud-native apps, you can choose a different database solution for telemetry data that's more suitable for streaming data, such as Cosmos DB, rather than a traditional, relational database that might be more suitable for an inventory service.
+Because of the loosely coupled nature of cloud-native apps, you can choose a different database solution for telemetry data that's more suitable for streaming data. For example, rather than using a traditional, relational database that might be more suitable for an inventory service, you could use Cosmos DB.
 
 :::column-end:::
 :::column span="1":::
diff --git a/learn-pr/azure/introduction-to-cloud-native-apps/includes/5-when-to-use-cloud-native-apps.md b/learn-pr/azure/introduction-to-cloud-native-apps/includes/5-when-to-use-cloud-native-apps.md
@@ -1,12 +1,12 @@
-Cloud-native apps are architecturally different to more traditional software engineering approaches. Because cloud-native is such a broad category, you can easily create an architecture to serve most needs, such as speed to market, integration of new technologies like machine learning, and rapid adaptation to customer feedback.
+Cloud-native apps are architecturally different to more traditional software engineering approaches. Because cloud-native is such a broad category, you can easily create an architecture to serve most needs. Such as, speed to market, integration of new technologies like machine learning, and rapid adaptation to customer feedback.
 
 ### Modernizing existing apps
 
 Cloud-native apps aren’t only for new projects. While a retrofit application might never be 'truly native to the cloud,' many existing applications would benefit from cloud-native thinking—allowing individual features to be released *without* a redeployment of the entire system, while still increasing reliability.
 
 It’s often cost-effective to cloud-optimize an existing application, as you can take better advantage of fine-grained scalability and improved system resiliency. Many cloud services provide administrative functionality suitable for cloud architects and developers, because it lowers the need for specialist management.
 
-For example, Azure Database for PostgreSQL has built-in database administrative functionality that is like DBA, by managing the underlying operating system and database for you.
+For example, Azure Database for PostgreSQL has built-in functionality that acts like a database administrator (DBA), managing the underlying operating system and database for you.
 
 ### Gradual adoption of a cloud-native approach
 
diff --git a/learn-pr/azure/introduction-to-cloud-native-apps/includes/7-summary.md b/learn-pr/azure/introduction-to-cloud-native-apps/includes/7-summary.md
@@ -2,15 +2,15 @@ In this module, you learned about cloud-native apps. You also learned about serv
 
 Cloud-native apps present a new, modern approach for building systems. If you want to learn more about containers, you can see [Introduction to Docker containers](/training/modules/intro-to-docker-containers/). If you want to learn more about how to orchestrate containers, you can see [Introduction to Kubernetes](/training/modules/intro-to-kubernetes/) and [Introduction to Azure Kubernetes Service](/training/modules/intro-to-azure-kubernetes-service/).
 
-Now that you've reviewed this module, you should be able to:
+Now that you reviewed this module, you should be able to:
 
-* Describe the fundamental structure of a Cloud Native App
-* Identify situations where you should build a Cloud Native App
+* Describe the fundamental structure of a Cloud Native App.
+* Identify situations where you should build a Cloud Native App.
 
 ## Use these resources to discover more
 
 [!include[](../../../includes/open-link-in-new-tab-note.md)]
 
 * [Introduction to Kubernetes on Azure](/training/paths/intro-to-kubernetes-on-azure/)
 * [Candidate apps for cloud native](/dotnet/architecture/cloud-native/candidate-apps)
-* [Modernize existing .NET applications with Azure cloud and Windows Containers](https://dotnet.microsoft.com/download/thank-you/modernizing-existing-net-apps-ebook)
+* [Downloadable PDF: Modernizing existing .NET applications with Azure cloud and Windows Containers](https://dotnet.microsoft.com/download/thank-you/modernizing-existing-net-apps-ebook)
diff --git a/learn-pr/azure/introduction-to-cloud-native-apps/index.yml b/learn-pr/azure/introduction-to-cloud-native-apps/index.yml
