Azure Architect

Shaping customer decisions to buy, architect and adopt Azure Infrastructure and Platform solutions

Duration

5 Days

Level

Intermediate Level

Design and Tailor this course

As per your team needs

Edit Content

While customers are progressively moving to public cloud, properly architecting cloud solutions, while managing how decisions in each area of networking, identity, security, business continuity, disaster recovery, data management, budgeting, and governance impact the overall cloud solution. This course is for professionals who advise stakeholders and transform business requirements into scalable, reliable, performant and secure cloud solutions.

Edit Content

The intended audience for this course

  • Cloud Architects
  • Enterprise Architects
  • Technical Architects
Edit Content
  • Identify security and legal compliances
  • Identifying Identity and access management requirements
  • Identifying non-functional requirements for scalability, security, availability, monitoring, back-ups, logging, auditing, SLAs and sizing
  • Capacity planning for various workloads
  • Designing the cloud physical architecture to cater for the gathered non-functional requirements
  • Estimate Azure sizing/pricing based on the above information
  • Planning for Identity and access management
  • Planning for authentication and authorization approaches
  • Planning for end-user self-service capabilities
  • Plan for Identity protection, security and conditional access including multi factor authentication and single SignOn
  • Defining access control based on role, rule and responsibility
  • Plan for managing the security posture on the entire Azure environment
  • Plan and design for metric based alert notifications triggered on specific events
  • Conduct cloud assessment to identify compatibility issues, if any
  • Conduct network bandwidth assessment
  • Design recovery policies and define Recovery Time Objective (RTO), Recovery Level Objective (RLO), Recovery Point Objective (RPO)
  • Batching workloads for failing-over to Azure based on applications
  • Modernizing network topology and design for High Availability, global distribution and auto-scaling
  • Design for Planned and Unplanned failover/failbacks
  • Securing and optimizing workloads post-migration
  • Planning for a Disaster Recovery site on Azure (Azure to Azure / On-prem to Azure)
  • Recommend data archival strategy based on the business compliance requirements
  • Identify the right data archival pricing tiers and identify SLAs
  • Recommend Azure compute options – App Services, Containers, VMs, AKS, Azure Service Fabric and so on
  • Recommend appropriate storage solutions and management tools
  • Design secure and scalable network topologies on Azure
  • Recommend network management tools
  • Recommend the right services for application and infrastructure level monitoring
  • How to work with development teams to identify the scope for application modernization?
  • Design for auto-scaling
  • Design for third party integrations – Cloud and On-Premise
  • Design for event-based triggers, asynchronous communication(messaging), API integrations
  • Recommend scope for serverless computing to save costs
Edit Content

The participants should have a basic knowledge of Linux/Unix commands

Connect

we'd love to have your feedback on your experience so far