Topic 1, Litware, inc.
Existing Environment
Litware has an Azure Active Directory (Azure AD) tenant that syncs with an Active Directory Domain Services (AD D%) forest named Utvvare.com and is linked to 20 Azure subscriptions. Azure AD Connect is used to implement pass-through authentication. Password hash synchronization is disabled, and password writeback is enabled. All Litware users have Microsoft 365 E5 licenses.
The environment also includes several AD DS forests, Azure AD tenants, and hundreds of Azure subscriptions that belong to the subsidiaries of Litware.
Planned Changes
Litware plans to implement the following changes:
* Create a management group hierarchy for each Azure AD tenant.
* Design a landing zone strategy to refactor the existing Azure environment of Litware and deploy all future Azure workloads.
* Implement Azure AD Application Proxy to provide secure access to internal applications that are currently accessed by using the VPN.
Business Requirements
Litware identifies the following business requirements:
* Minimize any additional on-premises infrastructure.
* Minimize the operational costs associated with administrative overhead.
Hybrid Requirements
Litware identifies the following hybrid cloud requirements:
* Enable the management of on-premises resources from Azure, including the following:
* Use Azure Policy for enforcement and compliance evaluation.
* Provide change tracking and asset inventory.
* Implement patch management.
* Provide centralized, cross-tenant subscription management without the overhead of maintaining guest accounts.
Microsoft Sentinel Requirements
Litware plans to leverage the security information and event management (SIEM) and security orchestration automated response (SOAK) capabilities of Microsoft Sentinel. The company wants to centralize Security Operations Center (SOQ by using Microsoft Sentinel.
Identity Requirements
Litware identifies the following identity requirements:
* Detect brute force attacks that directly target AD DS user accounts.
* Implement leaked credential detection in the Azure AD tenant of Litware.
* Prevent AD DS user accounts from being locked out by brute force attacks that target Azure AD user accounts.
* Implement delegated management of users and groups in the Azure AD tenant of Litware, including support for.
* The management of group properties, membership, and licensing
* The management of user properties, passwords, and licensing
* The delegation of user management based on business units.
Regulatory Compliance Requirements
Litware identifies the following regulatory compliance requirements:
* insure data residency compliance when collecting logs, telemetry, and data owned by each United States- and France-based subsidiary.
* Leverage built-in Azure Policy definitions to evaluate regulatory compliance across the entire managed environment.
* Use the principle of least privilege.
Azure Landing Zone Requirements
Litware identifies the following landing zone requirements:
* Route all internet-bound traffic from landing zones through Azure Firewall in a dedicated Azure subscription.
* Provide a secure score scoped to the landing zone.
* Ensure that the Azure virtual machines in each landing zone communicate with Azure App Service web apps in the same zone over the Microsoft backbone network, rather than over public endpoints.
* Minimize the possibility of data exfiltration.
* Maximize network bandwidth.
The landing zone architecture will include the dedicated subscription, which will serve as the hub for internet and hybrid connectivity. Each landing zone will have the following characteristics:
* Be created in a dedicated subscription.
* Use a DNS namespace of litware.com.
Application Security Requirements
Litware identifies the following application security requirements:
* Identify internal applications that will support single sign-on (SSO) by using Azure AD Application Proxy.
* Monitor and control access to Microsoft SharePoint Online and Exchange Online data in real time.

https://docs.microsoft.com/en-us/azure/app-service/app-service-ip-restrictions#restrict-access-to-a-specific-azure-front-door-instance