Adding POC Overview Section

microsoft · Oct 25, 2024 · c902474 · c902474
1 parent 7b62a49
commit c902474
Show file tree

Hide file tree

Showing 28 changed files with 201 additions and 42 deletions.
diff --git a/Scenarios/entra-suite-poc-overview.md b/Scenarios/entra-suite-poc-overview.md
@@ -1,54 +1,90 @@
-**<h1>Entra Suite POC Overview</h1>**
+# Entra Suite POC Overview
 
+## Microsoft Entra Suite Capabilities
 
-**<h2>Microsoft Entra Suite Capabilities</h2>**
+![image](../images/scope.png)
 
-![image](https://github.com/user-attachments/assets/9941f0f3-c0cc-48b7-8cfd-460346f1193e)
+## PoC | Timeline
 
-**<h2>PoC | Timeline</h2>**
+![image](../images/timeline.png)
 
-![image](https://github.com/user-attachments/assets/69a9b697-502d-4e76-bd1a-e90bfda11059)
-
-**<h2>Logistics</h2>**
+## Logistics
 
 - Each stage will only require participation of a subset of stakeholders from customers.
 - There are some pre-requisites for each scenario.
 - We recommend completing phases 2-4 as close together as feasible.
 
-
-**<h2>PoC | Pre-work</h2>**
+## PoC | Pre-work
 
 Identify resources to onboard. Recommendations:
+
 - Ensure all prerequisites are met for each scenario, and that the appropriate roles and stakeholders are available for this Proof of Concept (POC).
 
+## PoC | Phase 1: Intro
+
+![image](../images/Intro.png)
+
+| Role  | Responsability |  
+| ----- | -------- |
+| Microsoft Entra ID Global Admin | -> Activate trials and initial setup |
+| Security Team | -> Validate Entra suite secure access approach |
+| Network Team | -> Validate Entra suite secure access aproach  |
+| All mentioned roles above | -> Review Prerequisites and scenarios |
+
+**Table 1:** Roles for Intro phase
+
+## PoC | Phase 2: Enhanced workforce and guest lifecycle
 
-**<h2>PoC | Phase 1: Intro</h2>**
+![image](../images/scenario1.png)
 
-![image](https://github.com/user-attachments/assets/3d9a1b1e-a710-406c-b95a-a3624de2d829)
-![image](https://github.com/user-attachments/assets/ccb177d9-5c67-464c-8f0d-c613002c6352)
+| Role  | Responsability / Function |  
+| ----- | -------- |
+| Global Administrator or authentication policy administrator & application administrator | -> Configure Microsoft Entra Verified ID |
+| Global Administrator Or Security Administrator | -> Add trusted External Organization (For B2B Scenario - Optional) |
+| Global Administrator Or Identity Governance Administrator | -> Create Entitlement Management Catalog and Access Packages |
+| Test End User | -> Test and Validate user onboarding process |
 
+**Table 1:** Roles for Intro phase
 
-**<h2>PoC | Phase 2: Enhanced workforce and guest lifecycle</h2>**
+## PoC | Phase 3: Modernize remote access
 
-![image](https://github.com/user-attachments/assets/ecfccdcd-95ae-4d04-b845-aab22c56e1bf)
-![image](https://github.com/user-attachments/assets/ee4c5feb-da6e-4ce5-9df5-9156f1d39322)
+![image](../images/scenario2.png)
 
+| Role / Pre-requisite  | Responsability / Function |  
+| ----- | -------- |
+| Global Administrator | -> Configure Global Secure Access|
+| Groups or Users Administrator | -> Create test groups and users |
+| Windows client device - W10,W11 - Entra Joined or Hybrid Joined  | -> Client test for private access |
+| Windows Server 2012 R2 or later | -> Secure access connector server |
+| Test End User | -> Test and validate Entra private access |
 
+**Table 1:** Roles for Intro phase
 
-**<h2>PoC | Phase 3: Modernize remote access</h2>**
+## PoC | Phase 4: Govern Internet Access based on business needs
 
-![image](https://github.com/user-attachments/assets/5ae7eaa9-e50f-4621-9f18-1cdb36587a8a)
-![image](https://github.com/user-attachments/assets/14acadcd-439c-4723-8b5d-a5c1e5c75287)
+![image](../images/scenario3.png)
 
+| Role / Pre-requisite  | Responsability / Function |  
+| ----- | -------- |
+| Global Administrator | -> Configure Global Secure Access|
+| Groups or Users Administrator | -> Create test groups and users |
+| Windows client device - W10,W11 - Entra Joined or Hybrid Joined  | -> Client test for private access |
+| Test End User | -> Test and validate Entra internet access |
 
+**Table 1:** Roles for Intro phase
 
-**<h2>PoC | Phase 4: Govern Internet Access based on business needs</h2>**
+## PoC | Phase 5: Close-out
 
-![image](https://github.com/user-attachments/assets/531969ae-f452-4c54-b804-7bfdc89570d5)
-![image](https://github.com/user-attachments/assets/3adf1a8f-8a61-4187-89c2-eb6440c377e2)
+![image](../images/closeout.png)
 
+## Wrap-up session (1 hour)
 
+**Who?**
 
-**<h2>PoC | Phase 5: Close-out</h2>**
+    * All teams
+    * Leadership team
 
-![image](https://github.com/user-attachments/assets/5afd8b27-2760-49a6-88cf-f7cbca29f47f)
+**Goal**
+* Present top findings to leadership
+* Discuss strategy to further implement
+* Collect Feedback
diff --git a/TrainingHubs/TrainingHubs.md b/TrainingHubs/TrainingHubs.md
@@ -1,3 +1,7 @@
+---
+sidebar_position: 8
+title: Product Training Hubs
+---
 # Products Training Hubs
 
 Explore the products included in the Entra Suite with our Training Hubs and POC-in-a-Box resources

diff --git a/images/EntraSuiteOverall.png b/images/EntraSuiteOverall.png
diff --git a/images/EntraSuiteProducts.png b/images/EntraSuiteProducts.png
diff --git a/images/Intro.png b/images/Intro.png
diff --git a/images/closeout.png b/images/closeout.png
diff --git a/images/scenario1.png b/images/scenario1.png
diff --git a/images/scenario2.png b/images/scenario2.png
diff --git a/images/scenario3.png b/images/scenario3.png
diff --git a/images/scope.png b/images/scope.png
diff --git a/images/timeline.png b/images/timeline.png
diff --git a/website/docs/Partners/Partners.md b/website/docs/Partners/Partners.md
@@ -1,5 +1,5 @@
 ---
-sidebar_position: 4
+sidebar_position: 7
 title: Service Partners resources
 ---
 

diff --git a/website/docs/PublicDocs/docs.md b/website/docs/PublicDocs/docs.md
@@ -1,5 +1,5 @@
 ---
-sidebar_position: 5
+sidebar_position: 9
 title: Licensing and Documentation
 ---
 

diff --git a/website/docs/Scenarios/Readme.md b/website/docs/Scenarios/Readme.md
@@ -6,7 +6,7 @@ title: Entra Suite POC in a Box
 
 Explore our real-life scenarios that articulate the value of Microsoft Entra Suite and how its capabilities work together.
 
-- [Entra Suite POC Overview](../Assets/01-Entra_Suite_POC_Overview.pptx)
+- [Entra Suite POC Overview](./entra-suite-poc-overview.md)
 
 ### Microsoft Entra Suite Scenarios
 

diff --git a/website/docs/Scenarios/Scenario1.md b/website/docs/Scenarios/Scenario1.md
@@ -1,8 +1,14 @@
-# Microsoft Entra Suite Scenario 1
+---
+sidebar_position: 4
+title: Enhanced workforce and guest lifecycle
+---
+# Enhanced workforce and guest lifecycle
+
+> Secure and governed access to all applications and resources
 
-## Enhanced workforce and guest lifecycle (Secure and governed access to all applications and resources)
 ## Introduction
-In this guide, we describe how to configure Microsoft Entra Suite products for a scenario in which the fictional organization, Contoso, wants to hire new remote employees and provide them with secure and seamless access to necessary apps and resources. 
+
+In this guide, we describe how to configure Microsoft Entra Suite products for a scenario in which the fictional organization, Contoso, wants to hire new remote employees and provide them with secure and seamless access to necessary apps and resources.
 They want to invite and collaborate with external users (such as partners, vendors, or customers) and provide them with access to relevant apps and resources. 
 
 Contoso uses Microsoft Entra Verified ID to issue and verify digital proofs of identity and status for new remote employees (based on human resources data) and external users (based on email invitations). Digital wallets store identity proof and status to allow access to apps and resources. As an additional security measure, Contoso may verify identity with FaceCheck facial recognition based on the picture that the credential stores.
@@ -18,6 +24,7 @@ Employees and external users can request access packages through a self-service
 Contoso uses Microsoft Entra Identity Protection and Conditional Access (CA) to monitor and protect accounts from risky sign-ins and user behavior. They enforce appropriate access controls based on location, device, and risk level
 
 ## Configure prerequisites
+
 To successfully deploy and test the solution, configure the prerequisites that we describe in this section.
 Configure Microsoft Entra Verified ID
 For this scenario, complete these prerequisite steps to configure Microsoft Entra Verified ID with Quick setup (Preview):

diff --git a/website/docs/Scenarios/Scenario2.md b/website/docs/Scenarios/Scenario2.md
@@ -1,6 +1,11 @@
-# Microsoft Entra Suite Scenario 2
+---
+sidebar_position: 5
+title: Modernize remote access
+---
 
-## Modernize remote access (Secure and governed access to all applications and resources)
+# Modernize remote access
+
+> Secure and governed access to all applications and resources
 
 ## Introduction
 
@@ -13,6 +18,7 @@ Remote users can connect to private apps across hybrid and multi-cloud environme
 Microsoft Entra ID Protection cloud-based identity and access management (IAM) solution helps protect user identities and credentials from compromise.
 
 You can replicate these high-level steps for the Contoso solution as described in this guide.
+
 1.Sign up for Microsoft Entra Suite. Enable and configure Microsoft Entra Internet and Private Access to desired network and security settings.
 
 2.Deploy [Microsoft Global Secure Access client](https://learn.microsoft.com/en-us/entra/global-secure-access/how-to-install-windows-client) on user devices and [Microsoft Entra Private Access connector](https://learn.microsoft.com/en-us/entra/architecture/sse-deployment-guide-private-access)s on private networks. Include multi-cloud IaaS based virtual networks to access apps and resources on Contoso networks.

diff --git a/website/docs/Scenarios/Scenario3.md b/website/docs/Scenarios/Scenario3.md
@@ -1,6 +1,11 @@
-# Microsoft Entra Suite Scenario 3
+---
+sidebar_position: 6
+title: Govern internet access based on business needs
+---
 
-## Govern internet access based on business needs (Secure and governed access to all applications and resources)
+# Govern internet access based on business needs
+
+> Secure and governed access to all applications and resources
 
 ## Introduction
 
@@ -11,16 +16,22 @@ In an example scenario for which we describe how to configure its solution in th
 In another example scenario and corresponding solution, a SOC analyst needs to access a group of high-risk internet destinations for a specific time to investigate an incident. The SOC analyst can make that request in My Access. Upon approval, they become a member of a group that grants them access to high-risk internet destinations. 
 
 You can replicate these high-level steps for the Contoso solution as described in this guide.
-1.	Sign up for Microsoft Entra Suite. Enable and configure Microsoft Entra Internet Access for desired network and security settings.
-2.	Deploy [Microsoft Global Secure Access clients](https://learn.microsoft.com/en-us/entra/global-secure-access/concept-clients) on users� devices. Enable Microsoft Entra Internet Access.
-3.	Create a security profile and web content filtering policies with a restrictive baseline policy that blocks specific web categories and web destinations for all users.
-4.	Create a security profile and web content filtering policies that allows access to social networking sites.
-5.	Create a security profile that enables the Hacking web category. 
-6.	Use [Microsoft Entra ID Governance](https://learn.microsoft.com/en-us/entra/id-governance/identity-governance-overview) to allow users requesting access to access packages such as: 
+
+1. Sign up for Microsoft Entra Suite. Enable and configure Microsoft Entra Internet Access for desired network and security settings.
+
+2. Deploy [Microsoft Global Secure Access clients](https://learn.microsoft.com/en-us/entra/global-secure-access/concept-clients) on users� devices. Enable Microsoft Entra Internet Access.
+
+3. Create a security profile and web content filtering policies with a restrictive baseline policy that blocks specific web categories and web destinations for all users.
+
+4. Create a security profile and web content filtering policies that allows access to social networking sites.
+
+5. Create a security profile that enables the Hacking web category. 
+
+6. Use [Microsoft Entra ID Governance](https://learn.microsoft.com/en-us/entra/id-governance/identity-governance-overview) to allow users requesting access to access packages such as: 
     * Marketing department users can request access to social networking sites with a quarterly access review. 
     * SOC team members can request access to high-risk internet destinations with a time limit of eight hours.
-7.	Create and link two [Conditional Access policies](https://learn.microsoft.com/en-us/entra/identity/conditional-access/plan-conditional-access) using the Global Secure Access security profile session control. Scope the policy to groups of users for enforcement.
-8.	Confirm that traffic is appropriately granted with traffic logs in Global Secure Access. Ensure that Marketing department users can access the access package in the My Access portal.
+7. Create and link two [Conditional Access policies](https://learn.microsoft.com/en-us/entra/identity/conditional-access/plan-conditional-access) using the Global Secure Access security profile session control. Scope the policy to groups of users for enforcement.
+8. Confirm that traffic is appropriately granted with traffic logs in Global Secure Access. Ensure that Marketing department users can access the access package in the My Access portal.
 These are the benefits of using these solutions together:
     * **Least privilege access to internet destinations**. Reduce internet resource access to only what the user requires for their job role through the joiner/mover/leaver cycle. This approach reduces end user and device compromise risk.
     * **Simplified and unified management**. Manage network and security functions from a single cloud-based console, reducing complexity and cost of maintaining multiple solutions and appliances.

diff --git a/website/docs/Scenarios/entra-suite-poc-overview.md b/website/docs/Scenarios/entra-suite-poc-overview.md
@@ -0,0 +1,95 @@
+---
+sidebar_position: 3
+title: POC Overview
+---
+# Entra Suite POC Overview
+
+## Microsoft Entra Suite Capabilities
+
+![image](../images/scope.png)
+
+## PoC | Timeline
+
+![image](../images/timeline.png)
+
+## Logistics
+
+- Each stage will only require participation of a subset of stakeholders from customers.
+- There are some pre-requisites for each scenario.
+- We recommend completing phases 2-4 as close together as feasible.
+
+## PoC | Pre-work
+
+Identify resources to onboard. Recommendations:
+
+- Ensure all prerequisites are met for each scenario, and that the appropriate roles and stakeholders are available for this Proof of Concept (POC).
+
+## PoC | Phase 1: Intro
+
+![image](../images/Intro.png)
+
+| Role  | Responsability |  
+| ----- | -------- |
+| Microsoft Entra ID Global Admin | -> Activate trials and initial setup |
+| Security Team | -> Validate Entra suite secure access approach |
+| Network Team | -> Validate Entra suite secure access aproach  |
+| All mentioned roles above | -> Review Prerequisites and scenarios |
+
+**Table 1:** Roles for Intro phase
+
+## PoC | Phase 2: Enhanced workforce and guest lifecycle
+
+![image](../images/scenario1.png)
+
+| Role  | Responsability / Function |  
+| ----- | -------- |
+| Global Administrator or authentication policy administrator & application administrator | -> Configure Microsoft Entra Verified ID |
+| Global Administrator Or Security Administrator | -> Add trusted External Organization (For B2B Scenario - Optional) |
+| Global Administrator Or Identity Governance Administrator | -> Create Entitlement Management Catalog and Access Packages |
+| Test End User | -> Test and Validate user onboarding process |
+
+**Table 1:** Roles for Intro phase
+
+## PoC | Phase 3: Modernize remote access
+
+![image](../images/scenario2.png)
+
+| Role / Pre-requisite  | Responsability / Function |  
+| ----- | -------- |
+| Global Administrator | -> Configure Global Secure Access|
+| Groups or Users Administrator | -> Create test groups and users |
+| Windows client device - W10,W11 - Entra Joined or Hybrid Joined  | -> Client test for private access |
+| Windows Server 2012 R2 or later | -> Secure access connector server |
+| Test End User | -> Test and validate Entra private access |
+
+**Table 1:** Roles for Intro phase
+
+## PoC | Phase 4: Govern Internet Access based on business needs
+
+![image](../images/scenario3.png)
+
+| Role / Pre-requisite  | Responsability / Function |  
+| ----- | -------- |
+| Global Administrator | -> Configure Global Secure Access|
+| Groups or Users Administrator | -> Create test groups and users |
+| Windows client device - W10,W11 - Entra Joined or Hybrid Joined  | -> Client test for private access |
+| Test End User | -> Test and validate Entra internet access |
+
+**Table 1:** Roles for Intro phase
+
+## PoC | Phase 5: Close-out
+
+![image](../images/closeout.png)
+
+## Wrap-up session (1 hour)
+
+**Who?**
+
+    * All teams
+    * Leadership team
+
+**Goal**
+* Present top findings to leadership
+* Discuss strategy to further implement
+* Collect Feedback
+
diff --git a/website/docs/TrainingHubs/TrainingHubs.md b/website/docs/TrainingHubs/TrainingHubs.md
@@ -1,5 +1,5 @@
 ---
-sidebar_position: 3
+sidebar_position: 7
 title: Product Training Hubs
 ---
 # 🏫 Product Training Hubs

diff --git a/website/docs/images/EntraSuiteOverall.png b/website/docs/images/EntraSuiteOverall.png
diff --git a/website/docs/images/EntraSuiteProducts.png b/website/docs/images/EntraSuiteProducts.png
diff --git a/website/docs/images/Intro.png b/website/docs/images/Intro.png
diff --git a/website/docs/images/closeout.png b/website/docs/images/closeout.png
diff --git a/website/docs/images/scenario1.png b/website/docs/images/scenario1.png
diff --git a/website/docs/images/scenario2.png b/website/docs/images/scenario2.png
diff --git a/website/docs/images/scenario3.png b/website/docs/images/scenario3.png
diff --git a/website/docs/images/scope.png b/website/docs/images/scope.png
diff --git a/website/docs/images/timeline.png b/website/docs/images/timeline.png