AZ-305: Designing Microsoft Azure Infrastructure Solutions
https://www.pluralsight.com/courses/az-305-designing-microsoft-azure-infrastructure-solutions
by A Cloud Guru
Section I - Welcome to the Course
- Course Introduction
- Important Information about This Course
Section 2 - Architecting Azure Solutions
- Being a Solution Architect
- roles of a solution architect
- - initial requirements gathering
- - solution scoping and pricing
- - detailed solution design
- - solution implementation
- - handover to operations
- Azure Well-Architected Framework:
- A set of architectural pillars, which help when designing a modern cloud solution.
- Azure Architecture Center: A variety of patterns, practices, and guidelines for architecting solutions on Azure. Includes networking, hosting, applications, and more.
- Exploring the Cloud Adoption Framework
- Cloud Adoption Framework: a set of steps that Microsoft have put together to help you on being successful on Azure
- Service Map: Map communication between app components on Windows or Linux.
- TCO Calculator: Estimate monthly Azure running costs compared to on-premises.
- Azure Migrate: Tools for assessment and migration of machines, data, web apps, and more to Azure.
- Cost Management: Native Azure cost monitoring and reporting.
- Azure Advisor: Personalized recommendations ranging from performance to cost for your Azure resources.
- Azure Monitor: Centralized, multi-faceted monitoring platform for both Azure and on-premises resources.
Section 3 - Design Identity and Access Management
- Introduction
- identity is at the center of everything you do
- authentication vs authorization
- Recapping Azure AD
- you will have an azure subscription associated with an az ad tenant
- A tenant can be associated with multiple subscriptions
- A subscription is associated with only one tenant
- Identities: user account, application, managed identity
- To find applications registered with azure AD, from the azure portal go to Azure Active Directory then click on the App Registrations blade
- two types of security groups: assigned and dynamic
- Understanding Azure AD Hybrid Identities
- if you are looking for traditional on-premises Active Directory features, that aren't available for Azure AD, that's when you're probably going to use Azure AD Domain Services in the cloud.
- Azure AD Connect is for synchronizing user identities and passwords between on-premises AD and Azure AD to enable single sign-on (SSO) for cloud applications, migrate user identities to Azure AD, and manage user access to Azure resources
- Exploring Azure AD Extemal Identities
- for Azure B2B, you send an email invite to the external user
- shows how to invite an external user
- more external identity proviers are supported through Azure B2C than Azure AD B2B
- for Azure B2C, you need to create an Azure Active Directory B2C tenant resource
- you then switch into the new tenant and register your app and configure identity providers
- Recapping Azure Access Control
- azure rback and azure ad roles overview
- Scenario: Design for Identity and Access Management
- scenario of an app moving identity management to the cloud
- an azure B2C tenant supports local accounts as well as social accounts
Section 4 - Design for Identity Security
- Introduction
- Securing Identities with Azure AD Identity Protection
- az azure AD identity protection protects identities from being compromised
- requires azure ad premium p2 license
- demo of the Identity Protection resource
- demo of Sign-in risk policy
- demo of User risk policy
- explains difference between Sign-in risk policy and user risk policy
- Protecting Resources with Azure AD Conditional Access
- you need azure ad premium p1 licensing to use Conditional Access
- you can have multiple Conditional Access policies
- demo of creating Named Location
- demo of creating a Conditional Access Policy
- Protecting Privileges with Azure AD Privileged Identity Management (PIM)
- Designing Identity Govemance
- Scenario: Design for Identity Security
Section 5 - Design a Compute Strategy
- Introduction
- Architecting Virtual Machine-Based Solutions
- Architecting Container—Based Solutions
- Architecting Application Hosting in Azure
- Architecting Large-Scale Compute
- Isolating Compute-Based Solutions
- Scenario: Design a Compute Strategy
Section 6 - Design a Networking Strategy
- Introduction
- Recapping Virtual Networks
- Recapping Integrated Networks
- Recapping Hybrid Networks
- Designing Networks for Azure Services
- Scenario: Design a Networking Strategy
Section 7 - Design Connectivity and Security
- Introduction
- Recapping Azure Global Infrastructure
- Designing Highly Available Connectivity - Part I
- Designing Highly Available Connectivity - Part 2
- Exploring Network Security Services
- azure firewall has network rules, application rules and DNAT rules
- web based rules should go in application rules
- azure firewall manager lets you centralize firewall policies
- policies can be hierarchal
- the policies have to be in the same region but the firewalls can be anywhere
- WAF polcies are created per load balancer type: Application Gateway, Front Door, etc
- Scenario: Design Connectivity and Security
- gives scenario why you would use traffic manager over front door
- something to do with proxied vs direct call (huh?)
Section 8 - Design Apps for the Cloud
- Introduction
- Design Message-Driven Solutions
- azure queue storage is a component of azure storage
- - order not guarantied
- - message can only be up to 64kb
- service bus queues is a more advanced messaging service
- - messages can only be up to 100mb
- - order is guaranteed
- service buy topics allow you to implement publish/subscribe messaging
- - it allows you to have more than on recipient
- Design Event-Driven Solutions
- Event Grid is very similar to azure service bus topics
- demo of Event Grid
- Exploring Caching Services
- azure cdn is very similar to frontdoor
- besides microsoft's network, CDNs can use akamai or verizon
- Designing App Configuration and Deployments
- two types of ARM templates
- JSON
- bicep
- azure app configuration
- centrally store application settings for all app components
- Exploring Application Integration Services
- Exploring Azure AD App Proxy
- Scenario: Design Apps for the Cloud
Section 9 - Design Security for Apps in the Cloud
- Introduction
- Using Service Principals
- demo of create a client secret for a user principal
- demo of creating a storage account with a user principal and client secret
- Using Managed Identities
- Understanding API Security and OAuth 20
- Exploring Delegated Permissions and Consent - Part 1
- Exploring Delegated Permissions and Consent - Part 2
- Exploring Application Permissions and Consent
- Understanding Key Vault
- Scenario: Design Security for Apps in the Cloud
Section 10- Design Data Platforms
- Introduction
- Recapping Storage Accounts
- Recapping Azure Files Services
- Exploring Azure SQL Services
- Exploring Cosmos DB and Table Storage
- Scenario: Design Data Platforms
Section 11 - Design an Analytics Platform
- Introduction
- Exploring Azure Data Lake Storage
- Exploring Azure Analytics Services
- Exploring Azure Data Factory
- Exploring Azure Databricks
- Scenario: Design an Analytics Platform
Section 12 - Design Security for Data
- Introduction
- Controlling Access to Azure Storage
- Protecting Data in Azure Storage
- Controlling Access to Azure SQL Services
- Protecting Data in Azure SQL Services
- Scenario: Design Security for Data
Section 13 - Design Recovery and Resilience
- Introduction
- Design Recovery and Resilience for Azure Storage
- Design Recovery and Resilience for Azure SQL Services - Part I
- Design Recovery and Resilience for Azure SQL Services - Part 2
- Design Recovery and Resilience for Cosmos DB
- Back Up Workloads with Azure Backup
- Design for Business Continuity with Azure Site Recovery
- Scenario: Design Recovery and Resilience
Section 14 - Design Migrations
- Introduction
- Migrate Workloads with Azure Migrate
- Migrate Data with Database Migration Service
- Explore Azure Data Transfer Technologies
- Scenario: Design Migrations
Section 15 - Design Governance
- Introduction
- Organizing Azure Resources
- Organizing Azure AD
- Understanding Azure Policy
- Exploring Tools to Enforce Standards
- Scenario: Design Governance
Section 16 - Designing an Auditing and Monitoring Strategy
- Introduction
- Design Monitoring in Azure
- Exploring Logging and Retention
- Exploring Resource Monitoring Tools
- Design Monitoring for Security and Standards
- Design Monitoring Alerts and Actions
- Scenario: Design an Auditing and Monitoring Strategy
Section 17 - Final Steps
- Preparing for the Exam
- Course Completion
Comments
Post a Comment