Merge pull request #49708 from wwlpublish/159892b9a0f2ec9afe0b4b55a4e87b2e17c6543b845cea7638b18d08989ccd6d-live

v-ccolin · web-flow · commit ca790d0bfd9b · 2025-03-28T09:10:31.000Z
Modules/M03-explore-identity-azure-ad
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/1-introduction.yml b/learn-pr/wwl-azure/explore-identity-azure-active-directory/1-introduction.yml
@@ -4,7 +4,7 @@ title: Introduction
 metadata:
   title: Introduction
   description: "Introduction"
-  ms.date: 01/31/2024
+  ms.date: 03/28/2025
   author: wwlpublish
   ms.author: roberts
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/10-compare-microsoft-identity-providers.yml b/learn-pr/wwl-azure/explore-identity-azure-active-directory/10-compare-microsoft-identity-providers.yml
@@ -4,7 +4,7 @@ title: Compare Microsoft identity providers
 metadata:
   title: Compare Microsoft identity providers
   description: "Compare Microsoft identity providers"
-  ms.date: 01/31/2024
+  ms.date: 03/28/2025
   author: wwlpublish
   ms.author: roberts
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/11-define-identity-licensing.yml b/learn-pr/wwl-azure/explore-identity-azure-active-directory/11-define-identity-licensing.yml
@@ -4,7 +4,7 @@ title: Define identity licensing
 metadata:
   title: Define identity licensing
   description: "Define identity licensing"
-  ms.date: 01/31/2024
+  ms.date: 03/28/2025
   author: wwlpublish
   ms.author: roberts
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/12-explore-authentication.yml b/learn-pr/wwl-azure/explore-identity-azure-active-directory/12-explore-authentication.yml
@@ -4,7 +4,7 @@ title: Explore authentication
 metadata:
   title: Explore authentication
   description: "Explore authentication"
-  ms.date: 01/31/2024
+  ms.date: 03/28/2025
   author: wwlpublish
   ms.author: roberts
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/13-discuss-authorization.yml b/learn-pr/wwl-azure/explore-identity-azure-active-directory/13-discuss-authorization.yml
@@ -4,7 +4,7 @@ title: Discuss authorization
 metadata:
   title: Discuss authorization
   description: "Discuss authorization"
-  ms.date: 01/31/2024
+  ms.date: 03/28/2025
   author: wwlpublish
   ms.author: roberts
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/14-explain-auditing-identity.yml b/learn-pr/wwl-azure/explore-identity-azure-active-directory/14-explain-auditing-identity.yml
@@ -4,7 +4,7 @@ title: Explain auditing in identity
 metadata:
   title: Explain auditing in identity
   description: "Explain auditing in identity"
-  ms.date: 01/31/2024
+  ms.date: 03/28/2025
   author: wwlpublish
   ms.author: roberts
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/15-knowledge-check.yml b/learn-pr/wwl-azure/explore-identity-azure-active-directory/15-knowledge-check.yml
@@ -4,7 +4,7 @@ title: Knowledge check
 metadata:
   title: Knowledge check
   description: "Knowledge check"
-  ms.date: 01/31/2024
+  ms.date: 03/28/2025
   author: wwlpublish
   ms.author: roberts
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/16-summary.yml b/learn-pr/wwl-azure/explore-identity-azure-active-directory/16-summary.yml
@@ -4,7 +4,7 @@ title: Summary
 metadata:
   title: Summary
   description: "Summary"
-  ms.date: 01/31/2024
+  ms.date: 03/28/2025
   author: wwlpublish
   ms.author: roberts
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/2-explain-identity-landscape.yml b/learn-pr/wwl-azure/explore-identity-azure-active-directory/2-explain-identity-landscape.yml
@@ -4,7 +4,7 @@ title: Explain the identity landscape
 metadata:
   title: Explain the identity landscape
   description: "Explain the identity landscape"
-  ms.date: 01/31/2024
+  ms.date: 03/28/2025
   author: wwlpublish
   ms.author: roberts
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/3-explore-zero-trust-identity.yml b/learn-pr/wwl-azure/explore-identity-azure-active-directory/3-explore-zero-trust-identity.yml
@@ -1,10 +1,10 @@
 ### YamlMime:ModuleUnit
 uid: learn.wwl.explore-identity-azure-active-directory.explore-zero-trust-identity
-title: Explore zero trust with identity
+title: Explore Zero Trust with identity
 metadata:
-  title: Explore zero trust with identity
-  description: "Explore zero trust with identity"
-  ms.date: 01/31/2024
+  title: Explore Zero Trust with identity
+  description: "Explore Zero Trust with identity"
+  ms.date: 03/28/2025
   author: wwlpublish
   ms.author: roberts
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/4-discuss-identity-control-plane.yml b/learn-pr/wwl-azure/explore-identity-azure-active-directory/4-discuss-identity-control-plane.yml
@@ -4,7 +4,7 @@ title: Discuss identity as a control plane
 metadata:
   title: Discuss identity as a control plane
   description: "Discuss identity as a control plane"
-  ms.date: 01/31/2024
+  ms.date: 03/28/2025
   author: wwlpublish
   ms.author: roberts
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/5-explore-why-have-identity.yml b/learn-pr/wwl-azure/explore-identity-azure-active-directory/5-explore-why-have-identity.yml
@@ -4,7 +4,7 @@ title: Explore why we have identity
 metadata:
   title: Explore why we have identity
   description: "Explore why we have identity"
-  ms.date: 01/31/2024
+  ms.date: 03/28/2025
   author: wwlpublish
   ms.author: roberts
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/6-define-identity-administration.yml b/learn-pr/wwl-azure/explore-identity-azure-active-directory/6-define-identity-administration.yml
@@ -4,7 +4,7 @@ title: Define identity administration
 metadata:
   title: Define identity administration
   description: "Define identity administration"
-  ms.date: 01/31/2024
+  ms.date: 03/28/2025
   author: wwlpublish
   ms.author: roberts
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/7-contrast-decentralized-identity-central-identity-systems.yml b/learn-pr/wwl-azure/explore-identity-azure-active-directory/7-contrast-decentralized-identity-central-identity-systems.yml
@@ -4,7 +4,7 @@ title: Contrast decentralized identity with central identity systems
 metadata:
   title: Contrast decentralized identity with central identity systems
   description: "Contrast decentralized identity with central identity systems"
-  ms.date: 01/31/2024
+  ms.date: 03/28/2025
   author: wwlpublish
   ms.author: roberts
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/8-discuss-identity-management-solutions.yml b/learn-pr/wwl-azure/explore-identity-azure-active-directory/8-discuss-identity-management-solutions.yml
@@ -4,7 +4,7 @@ title: Discuss identity management solutions
 metadata:
   title: Discuss identity management solutions
   description: "Discuss identity management solutions"
-  ms.date: 01/31/2024
+  ms.date: 03/28/2025
   author: wwlpublish
   ms.author: roberts
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/9-explain-business-to-business.yml b/learn-pr/wwl-azure/explore-identity-azure-active-directory/9-explain-business-to-business.yml
@@ -4,7 +4,7 @@ title: Explain Microsoft Entra Business to Business
 metadata:
   title: Explain Microsoft Entra Business to Business
   description: "Explain Microsoft Entra Business to Business"
-  ms.date: 01/31/2024
+  ms.date: 03/28/2025
   author: wwlpublish
   ms.author: roberts
   ms.topic: unit
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/includes/1-introduction.md b/learn-pr/wwl-azure/explore-identity-azure-active-directory/includes/1-introduction.md
@@ -1,34 +1,19 @@
 This module covers a wide view of the definitions and available services for identity provided in the Microsoft Cloud from Microsoft Entra ID to Microsoft 365.  You start with the basics of authentication, authorization, and access tokens.
 
-From this firm foundation of what an identity is, we explore how identity is used as part of your security foundation. We learn about governance and lifecycle management of your identities and identity solutions. The final section opens up the concept of zero trust, and how it should be applied to your identity solutions. What is the Microsoft Entra ID architecture and the connection with identity in Microsoft 365?
+From this firm foundation of what an identity is, we explore how identity is used as part of your security foundation. We learn about governance and lifecycle management of your identities and identity solutions. The final section opens up the concept of Zero Trust, and how it should be applied to your identity solutions. What is the Microsoft Entra ID architecture and the connection with identity in Microsoft 365?
 
 Next you explore how PowerShell and Microsoft Graph are available to build and manage identity solutions. The goal of this module is to prepare your technical knowledge of identity and access management in the Microsoft Cloud.
 
-In this module, you will:
-- Define the concept of central identity system and decentralized identity
-- Review systems of authentication and authorization in Microsoft Entra ID
-- Explore identity governance, and identity lifecycle management
-- Define the value of identity audits (reporting, monitoring)
-- Review how cryptography is used in identity (encryption, hashing)
-- Describe federated identity concepts (for example SAML)
-- Describe the different management automation interfaces PowerShell, CLI, and Graph API
-- Describe Zero Trust concepts
-- Describe Microsoft Entra ID architecture and its relationship with Microsoft 365
-- Define an identity provider and identity as a control plane
-- Compare different identity services - Microsoft Entra ID, Microsoft Entra DS, AD DS
-- Explain Microsoft Entra business-to-busines (B2B) and business-to-customer (B2C)
-- Review licenses to run an identity solution in the Microsoft Cloud
-
-
 ### Learning objectives
 
 By the end of this module can:
 
-- Define common identity terms and explain how they're used in the Microsoft Cloud
-- Explore the common management tools and needs of an identity solution
-- Explain the goal of Zero Trust and how it applies to identity in the Microsoft Cloud
-- Explore the available identity services in the Microsoft Cloud
+- Define common identity terms and explain how they're used in the Microsoft Cloud.
+- Explore the common management tools and needs of an identity solution.
+- Explain the goal of Zero Trust and how it applies to identity in the Microsoft Cloud.
+- Explore the available identity services in the Microsoft Cloud.
 
 ### Prerequisites
 
-None
+- Basic knowledge of cloud computing
+- Azure portal or Microsoft Entra admin center experience is a plus
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/includes/15-knowledge-check.md b/learn-pr/wwl-azure/explore-identity-azure-active-directory/includes/15-knowledge-check.md
@@ -1 +1,2 @@
-Choose the best response for each of the questions below. 
+
+Choose the best response for each of the questions below.
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/includes/2-explain-identity-landscape.md b/learn-pr/wwl-azure/explore-identity-azure-active-directory/includes/2-explain-identity-landscape.md
@@ -1,8 +1,8 @@
-It's important to understand the identity landscape before reviewing other identity concepts.  How does Microsoft think about identity when designing products and solutions? The essential lifecycle of identity.
+It's important to understand the identity landscape before reviewing other identity concepts. How does Microsoft think about identity when designing products and solutions? The essential lifecycle of identity.
 
 | 1) Zero Trust |
 |:--------------------------:|
-| :::image type="icon" source="../media/icon-verify-explicitly.png" alt-text="Diagram showing a mock-up checklist to show you're verifying each record.":::Verify Explicitly      :::image type="content" source="../media/icon-least-privilege.png" alt-text="Decoration. Icon of a simple circuit showing that you should only grant the least level of access needed.":::Use Least Privilege   :::image type="content" source="../media/icon-assume-breach.png" alt-text="Decoration. Icon of two arrows with points together showing a point where a breach might have occurred.":::Assume Breach |
+| :::image type="icon" source="../media/icon-verify-explicitly.png" alt-text="Diagram showing a mock-up checklist to show you're verifying each record.":::Verify Explicitly      :::image type="content" source="../media/icon-least-privilege.png" alt-text="Decoration. Icon of a simple circuit showing that you should only grant the least level of access needed.":::Use Least Privilege   :::image type="content" source="../media/icon-assume-breach.png" alt-text="Decoration. Icon of two arrows with points together showing a point where a breach potentially occurred.":::Assume Breach |
 
 | 2) Identity                  | 3) Actions                       |
 |:--------------------------- |:------------------------------- |
@@ -18,23 +18,23 @@ It's important to understand the identity landscape before reviewing other ident
 | Dollars - Licenses           | |
 
 
-**First** you have the guidance of always thinking and designing with zero trust in mind.  Don't just give access to data and applications because the user has had access previously.  You need to always confirm.
+1) **First** you have the guidance of always thinking and designing with Zero Trust in mind. Don't just give access to data and applications because the user had access previously. You need to always confirm.
 
-**Second** you have systems to provide verified accounts for users and applications.  Identity services come from Microsoft Entra ID, from business-to-business federation, from business-to-customer, and from decentralized identity providers.
+2) **Second** you have systems to provide verified accounts for users and applications. Identity services come from Microsoft Entra ID, from business-to-business federation, from business-to-customer, and from decentralized identity providers.
 
-**Third** you have specific actions identity provides and to keep the systems running.  Users and applications can authenticate and authorize to gain access to systems.  And administrators need to monitor and maintain the identity systems with proper governance.
+3) **Third** you have specific actions identity provides and to keep the systems running. Users and applications can authenticate and authorize to gain access to systems. And administrators need to monitor and maintain the identity systems with proper governance.
 
-**Fourth** you get many actions that can be performed once your credentials are verified.  Use applications and data, while taking advantage of other identity based services.
+4) **Fourth** you get many actions that can be performed once your credentials are verified. Use applications and data, while taking advantage of other identity based services.
 
-**Fifth** and finally, you need to always keep your systems up to date.
+5) **Fifth** and finally, you need to always keep your systems up to date.
 
-### From classic identity to zero trust identity
+### From classic identity to Zero Trust identity
 
-Historically, identity kept all your assets behind the firewall.  Submit a username and password to get through the gate, and you had full access to everything.  In the modern world, with the large number of cyber-attacks securing just the network doesn't work.  One lost or stolen credential and bad actors have access to everything.  With zero trust, you protect your assets anywhere with policy.
+Historically, identity kept all your assets behind the firewall. Submit a username and password to get through the gate, and you had full access to everything. In the modern world, with the large number of cyber-attacks securing just the network doesn't work. One lost or stolen credential and bad actors have access to everything. With Zero Trust, you protect your assets anywhere with policy.
 
-| Classic identity | Zero trust identity |
+| Classic identity | Zero Trust identity |
 | :--------------- | :------------- |
 | :::image type="content" source="../media/classic-identity.png" alt-text="Diagram of a set of assets like a database and an application protected behind a locked gate."::: | :::image type="content" source="../media/zero-trust-identity.png" alt-text="Diagram of a central policy in the form of a chart, giving access to different locally protected resources."::: |
 | Restrict everything to a secure network | Protect assets anywhere with central policy |
 
-Each of these subjects will be covered in more detail over the rest of this module.
+Each of these subjects is covered in more detail over the rest of this module.
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/includes/3-explore-zero-trust-identity.md b/learn-pr/wwl-azure/explore-identity-azure-active-directory/includes/3-explore-zero-trust-identity.md
@@ -19,7 +19,7 @@ A Zero Trust approach should extend throughout the entire digital estate and ser
 
 :::image type="content" source="../media/zero-trust-pillars.png" alt-text="Diagram of the six pillars of Zero Trust.  Identity - endpoints - data - apps - infrastructure - and network.":::
 
-For this content, we're going to focus specifically on the **security identity with zero trust** pillar. Identities, whether they represent people, services, or IoT devices define the Zero Trust control plane. When an identity attempts to access a resource, verify that identity with strong authentication, and ensure access is compliant and typical for that identity. Follow least privilege access principles.
+For this content, we're going to focus specifically on the **security identity with Zero Trust** pillar. Identities, whether they represent people, services, or IoT devices define the Zero Trust control plane. When an identity attempts to access a resource, verify that identity with strong authentication, and ensure access is compliant and typical for that identity. Follow least privilege access principles.
 
 ### Zero Trust architecture
 
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/includes/4-discuss-identity-control-plane.md b/learn-pr/wwl-azure/explore-identity-azure-active-directory/includes/4-discuss-identity-control-plane.md
@@ -1,6 +1,5 @@
 :::image type="content" source="../media/control-plane.png" alt-text="Diagram of identity and access management working as a controller for access to all resource.":::
 
-First, we should probably answer the question - what is a control plane?  A **control plane** is a term that has been used for years within networks.  It's the part of a network that routes network traffic around the network architecture.  So, a control plane is a tool or service that directs access to resources based on specific criteria.  When it comes to solutions in today's world, the user identity is the right place to check for access.  This sets up identity as the control plane. 
-
-With the many networks, devices, and applications needed in daily business, the only common denominator is the user. This is why we say, Identity is the control plane. It’s critical to establish who the user is as the core of trust for other transactions. If we aren’t sure who the user is, no other system access control or security matters. Once we're sure of the user, we can explicitly verify every element of access whether our resources are on-premises, in cloud-hosted servers, or managed by third-party SaaS apps like Office 365.
+What is a control plane?  A **control plane** is a term that used for years within networks. It's the part of a network that routes network traffic around the network architecture. So, a control plane is a tool or service that directs access to resources based on specific criteria. When it comes to solutions in today's world, the user identity is the right place to check for access. Identity is a clear choice for the control plane.
 
+With the many networks, devices, and applications needed in daily business, the only common denominator is the identity. Every user, external user, app, and device have an identity. So, we say identity is the control plane. It’s critical to establish who the user is as the core of trust for other transactions. If we aren’t sure who the user is, no other system access control or security matters. Once we're sure of the user, we can explicitly verify every element of access whether our resources are on-premises, in cloud-hosted servers, or managed SaaS apps like Office 365.
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/includes/5-explore-why-have-identity.md b/learn-pr/wwl-azure/explore-identity-azure-active-directory/includes/5-explore-why-have-identity.md
@@ -24,12 +24,10 @@ An identity provider (IdP) is a system that creates, manages and stores digital
 - Security protocols that defend against intrusion
 - Someone we trust
 
-An identity provider verifies user identities using one or more authentication factors, such as a password or fingerprint scan.  An identity provider is often a trusted provider for use with single-sign-on (SSO) to access other resources. SSO enhances usability by reducing password fatigue. It also provides better security by decreasing the potential attack surface. Identity providers can facilitate connections between cloud computing resources and users, thus decreasing the need for users to reauthenticate when using mobile and roaming applications.
+An identity provider verifies identities using one or more authentication factors, such as a password or fingerprint scan.  An identity provider is often a trusted provider for use with single-sign-on (SSO) to access other resources. SSO enhances usability by reducing password fatigue. It also provides better security by decreasing the potential attack surface. Identity providers can facilitate connections between cloud computing resources and users, thus decreasing the need for users to reauthenticate when using mobile and roaming applications.
 
 ### Common identity protocols
 
 **OpenID provider** - OpenID Connect (OIDC) is an authentication protocol based on the OAuth2 protocol (which is used for authorization). OIDC uses the standardized message flows from OAuth2 to provide identity services. Specifically, a system entity (called an OpenID-Provider) issues JSON-formatted identity tokens to OIDC relying parties via a RESTful HTTP API.
 
 **SAML identity provider** - Security Assertion Markup Language (SAML) is an open standard for exchanging authentication and authorization data between an identity provider and a service provider. SAML is an XML-based markup language for security assertions, which are statements that service providers use to make access-control decisions.
-
-
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/includes/6-define-identity-administration.md b/learn-pr/wwl-azure/explore-identity-azure-active-directory/includes/6-define-identity-administration.md
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/includes/7-contrast-decentralized-identity-central-identity-systems.md b/learn-pr/wwl-azure/explore-identity-azure-active-directory/includes/7-contrast-decentralized-identity-central-identity-systems.md
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/includes/8-discuss-identity-management-solutions.md b/learn-pr/wwl-azure/explore-identity-azure-active-directory/includes/8-discuss-identity-management-solutions.md
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/index.yml b/learn-pr/wwl-azure/explore-identity-azure-active-directory/index.yml
diff --git a/learn-pr/wwl-azure/explore-identity-azure-active-directory/media/identity-basic-architecture.png b/learn-pr/wwl-azure/explore-identity-azure-active-directory/media/identity-basic-architecture.png
