Driving Continuous

Evolution of Azure
Environments

April 5th 2022

Agenda
Azure Service Retirements
Identifying & Modernizing Legacy Resources

Padi Quesnell
Azure Engineering
Azure retirements
 Azure is 12 years old; retirements are part of the natural lifecycle of any service or feature
 Retirements do not mean that all Azure customers are impacted
 Continuous innovation and modernization of Azure services helps unlock new and better opportunities
 It is our commitment to provide customers as much time and information, to plan thoughtfully

Minimum 12-month notice Targeted communications Initial retirement notification

to remove any material feature
or functionality, or discontinue
a service*
Minimum 90-day notice to retire
anything else
Modern Lifyecycle Policy
Online Services Terms
*excluding Previews
directly to active usage
Azure subscriptions
Viewable by anyone with admin
permissions on subscription
Authenticated
per policy
• Health advisory message in
Azure Service Health* Reminder messages at T-6
• Direct email to admins months, T-3 months, T-1 month,
then weekly until T-0
Unauthenticated
• Azure Updates post Will send an update notification if
• Banner messages on retiring any plans significantly change
service pages
*Set up a Service Health Alert to receive an
email, text, vmail, as well
Classic (IaaS) Compute Market Notification & Support Guidance

Migrate your IaaS resources to Azure Resource Overview of platform-supported migration of IaaS
Manager by March 1, 2023 | Azure updates | resources from classic to Azure Resource Manager -
Microsoft Azure
Azure Virtual Machines | Microsoft Docs
Cloud Services (PaaS) Market Notification & Support Guidance

Cloud Services (classic) deployment model is retiring Migrate Azure Cloud Services (classic) to Azure Cloud
on 31 August 2024 | Azure updates | Microsoft Azure Services (extended support) | Microsoft Docs
What is ASM Classic Compute vs Cloud Services (Classic)?
ASM supports two different compute products, Azure Virtual Machines (classic) also known as IaaS VMs
& Azure Cloud Services (classic) also known as PaaS VMs or Web/Worker Roles

Azure originally provided only the classic
deployment model. In this model, each resource
existed independently; there was no way to group
related resources together. Instead, you had to
manually track which resources made up your
solution or application, and remember to manage
them in a coordinated approach. The Azure Virtual
Machine (classic) is based on the old Azure Service
Management Model (ASM). Which revolved around
the concept of a cloud service. Everything was
contained inside a cloud service, and that was the
gateway to the internet. In 2014, Azure introduced
Resource Manager, which added the concept of a
resource group. A resource group is a container for
resources that share a common lifecycle.
Resource Manager and classic deployment - Azure Resource Manager |
Microsoft Docs
Azure Cloud Services is an example of a platform
as a service (PaaS). Like Azure App Service, this
technology is designed to support applications that
are scalable, reliable, and inexpensive to operate. In
the same way that App Service is hosted on virtual
machines (VMs), so too is Azure Cloud Services.
However, you have more control over the VMs. You
can install your own software on VMs that use
Azure Cloud Services, and you can access them
remotely.
What is Azure Cloud Services (classic) | Microsoft Docs
 migrate your customers IaaS
VMs

migrate them to Cloud Services (extended

support)

Azure Service Health Alerts

Well-Architected Review Assessment

Timeline Tracking period of
customer drop-off
Reminder:
Field, Partner &
Customer Pro-
active comms
from ANZ
March 2023

ASM Classic (IaaS)

ASM Classic (IaaS) Deprecation Date
Deprecation March 2023
announcement
Feb’2020

Azure Resource Manager

ASM Classic Cloud Reminder:
(ARM) Launched Classic Cloud Services
Services (PaaS) Field, Partner &
2014 replacing ASM (PaaS) Deprecation Date
Deprecation Customer Pro-active August 2024
announcement comms from ANZ
Aug’2021 Subsidiary
April 2022
 Learn more about the Learn more about the Get answers from Watch the FastTrack for
retirement of IaaS VM retirement of Cloud community experts in Azure FTA Live: Azure
management through Services (classic) Microsoft Q&A. Service Manager Migration
Azure Service Manager. deployment model. to learn more on
modernising Azure Classic
Services – Available on
Demand
Plan to Migrate
Steps to plan and execute the migration:
1. Make a list of all affected VMs. Also include list of other classic resources like storage
accounts (classic), vnet (classic), etc. attached to the VMs and needs to be migrated.
(Use Azure Resource Graph or PowerShell)

2. Learn more about the platform supported migration tool provided by Microsoft and
how it works.

3. Learn about how to handle unsupported scenarios or migration errors.

4. Plan for the migration & test the plan. Start with the provided migration tool. If tool
isn’t suitable, customers can perform lift & shift migration to ARM VMs or other
compute offerings.

5. Get help from Fast Track, CSAs, TAMs to help plan, test and execute the migration.

6. Start the migration and complete it before March 1st, 2023.

FAQ Doco:
7. Use free support if needed to help handle service impacts.
https://aka.ms/AAgiq8u
8. Add an automated Classic Services check to new customers you might onboard in
the next year (PowerShell or CLI)
How to Migrate
Steps to migrate virtual machines using platform supported migration
tool:
1. Go to the Virtual machines (classic) Portal Blade.

2. Under Subscriptions, select all available subscriptions to get full list of affected
classic VMs. Select one

3. Click on Migrate to ARM.

4. Register the Migration Resource Provider

5. Click on Validate. If validate failed, use the suggested methods in the error messages
or at Migration Overview document to fix the errors.

6. Click on Prepare. If prepare failed, use the suggested methods in the error messages
or at Migration Overview document to fix the errors.

7. View migrated virtual machines at Virtual Machines Portal Blade and Test their Free Migration Support:
operation. https://aka.ms/AAgiypb
8. (Optional) Click on Abort to rollback migration.

9. Click on Commit. Commit finalizes the migration and cannot be rolled back.
https://aka.ms/AAgiq8u
Cloud Services; Classic vs Extended Support
Cloud Services (extended support) is the Azure Resource Manager (ARM) supported
deployment model for Cloud Services (classic).

Benefits include:

Extended support before Role based access control, Feature parity between Cloud
deprecation of Cloud Services tagging, policy definitions and Services (classic) and Cloud
(classic) resource type supported deployment using Services (extended support)
ARM templates
Finding Cloud Service (classic) Resources
 On the Azure Portal, search for Cloud Services (classic) resource or
use Azure Resource Graph Explorer/Azure CLI/Azure PowerShell
 Use filters to locate Cloud Service (classic) resources across your
Azure environments
Migrating from Cloud Services (classic) to Cloud
Services (extended support)
Redeploy
• Customers can deploy a new cloud service directly
in Azure Resource Manager and then delete the old
cloud service in Azure Service Manager thorough
validation.
• Redeploy allows customers to:
• Define resource names.
• Organize or reuse resources as preferred.
• Reuse service configuration and definition
files with minimal changes.
• Traffic need to orchestrated to the new
deployment.
• Customers need to delete the old cloud services in
Azure Resource Manager.
• This is a lift and shift migration which offers more
flexibility but requires additional time to migrate.
Migrate Azure Cloud Services (classic) to Azure Cloud Services (extended support) | Microsoft Docs
In-place Migration
• In-place migration tool enables for a seamless
migration of existing Cloud Services (classic)
deployments to Cloud Services (extended support)
• For in-place migration, the platform:
• Defines resource names.
• Organizes each deployment and related
resources in individual Resource Groups.
• Modifies existing configuration and definition
file for Azure Resource Manager.
• Migration retains IP address and data path remains
the same.
• Platform deletes the Cloud Services (classic) resources
after migration.
• This is an automated migration which offers quick
migration but less flexibility.
Alternative
Compute Options
 Virtual machine scale
sets
 Azure Kubernetes
Service (AKS)
 Azure App Service
 And more…
https://aka.ms/comparecompute
Driving Continuous Evolution of
Azure Environments
The Opportunity for MSPs
Managed Service Delivery Needs to Change

“As currently structured, managed services are one of the

greatest impediments to digital transformation”
Has the cloud made managed services obsolete? (kpmg.us)

“Managed Service Providers must establish a customer

success mindset and lead with continuous innovation
to keep clients engaged in the long run.”
https://blogs.gartner.com/rene-buest/2020/03/06/managed-service-
provider-drive-customer-success-continuous-engagement/
Static, On-prem
environments Needed Today
• Reactive: • Dynamic Cloud
• Insurance policy: fix Environment
things if they go wrong • Continual Innovation
• Proactive: • Thought Leadership
• DR: Backups • Guidance on tech best
• Server patching practice
• Performance & • Agile & Proactive
availability monitoring
For customers, managing hybrid IT environments is complex
Service providers want less complexity, more automation and comprehensive tooling to grow their business

Pains Motivators

Lack of skilled Optimize costs with Pace of change & Meeting compliance Reduced security Control and
IT resources rapid migration increased complexity requirements exposure transparency
Customer to cloud
 141%
3-yr ROI

Azure Managed
Services opportunity 49%
Gross margin

58%
Margin

Note: Based on Forrester TEI study 2020 completed in June 2020​

Are you doing a good job as an MSP?

Do I understand my customer’s digital transformation strategy?

What is the next step in their journey?

Ask Are my customer’s workloads resilient, performant, cost effective, secure?

Is my customer aware of the latest Azure features & services?

Am I providing the best technical leadership to support their goals?

Cloud Adoption Framework
for Azure | Overview
Microsoft Cloud Adoption Framework for Azure
Proven guidance to accelerate your cloud adoption journey

Define strategy Plan Ready Adopt

Define business Align actionable cloud Prepare people, process Migrate or Innovate
justification and expected adoption plan to and environment for Implement desired changes
outcomes business outcomes change across IT and business
processes

Govern Manage
Comply, control and Operate and optimize
secure

https://aka.ms/adopt
Define strategy
Cloud journey tracker
Business outcome template
aka.ms/adopt/tools-templates
Plan Ready Adopt
Cloud adoption plan generator Azure setup guide Strategic migration assessment
and readiness tool (SMART)
Azure DevOps demo generator Readiness checklist
Azure migration guide
Cloud adoption plan template Naming and tagging tracking
template Azure innovation guide
Landing zone blueprints
Govern Manage
Governance benchmark Azure architecture review
Governance process template Best practices source code
Cost Management process template Operations management workbook
Deployment acceleration process template
Identity process template
Resource consistency process template
Security baseline process template
 Partner &
Service Offers

Cost
Optimization Azure Well-
Documentation Architected
Review

Well-Architected Security Operational

Excellence

at Microsoft
Reliability
Performance
Efficiency
Reference Design
Architectures Principles

Azure Advisor
 Microsoft Azure Well-Architected Framework
Architecture guidance and best practices, created for architects,
developers and solution owners, to improve the quality of their workloads,
based on 5 aligned and connected pillars

Cost Operational Performance Reliability Security

Optimization Excellence Efficiency

https://aka.ms/architecture/framework
 Overcoming workload quality inhibitors
Cost Operational Performance Reliability Security
Optimization Excellence Efficiency

• No cost and usage • Lack of rapid issue
monitoring identification
• Unclear on underused or • No deployment
orphaned resources automation
• Lack of structure billing • Absence of communication
management mechanisms and
• Budget reductions due to dashboards
lack of support for cloud • Unclear expectations and
adoption by LT/board business outcomes
• No visibility on root cause
for events
• No monitoring new
services
• No monitoring current
workloads health
• No design for scaling
• Lack of rigor and guidance
for technology and
architecture selection
• Unclear on resiliency
features/capabilities for
better architecture design
• Lack of data back up
practices
• No monitoring current
workloads health
• No resiliency testing
• No support for disaster
recovery
• No access control
mechanism
(authentication)
• No security thread
detection mechanism
• Lack of security thread
response plan
• No encryption process

https://aka.ms/architecture/framework
 Best practices to drive workload quality
Cost Operational Performance Reliability Security
Optimization Excellence Efficiency

✓ Azure Hybrid ✓ DevOps ✓ Design for scaling ✓ Define ✓ Identity and access
Benefit ✓ Deployment ✓ Monitor requirements management
✓ Reserve Instances ✓ Monitor performance ✓ Test with ✓ Infra protection
✓ Shutdown ✓ Processes and simulations and ✓ App security
✓ Resize cadence forced failovers ✓ Data encryption
✓ Move to PAAS ✓ Deploy and sovereignty
consistently ✓ Security operations
✓ Monitor health
✓ Respond to failure
https://aka.ms/architecture/framework and disaster
Well-Architected Review
Online Tool

Assess your workloads using the tenets found

in the Microsoft Azure Well-Architected
Framework:
• Understand the Well-Architected level of your
workload environment.

• Access guidance for next steps of your workload

improvement process.

aka.ms/wellarchitected/review
How can you get started?

Optimize existing workloads

Design & deploy new workloads

 Leverage Azure Advisor Score to identify

optimization opportunities
 Understand changes needed or incidents
occurred
 Leverage the Azure Well-Architected Review
to assess workload architecture design
 Consider architecture design trade offs to
achieve business goals
 Define and implement recommendations
 Establish a regular cadence for workload
optimization
 business
priorities
 Well-Architected Framework
Documentation
 Leverage the Azure Well-Architected Review to
assess workload architecture design
 Consider architecture design trade offs to
achieve business goals
 Build, deploy and manage workloads on Azure
Azure Advisor
Practical recommendations
based on your usage and
configurations, such as:
• Alerts to notify you about new
recommendations.

• Best practices to optimise your

Azure workloads.

• Step-by-step guidance and quick

actions for fast remediation.

• Azure Advisor is available at no

additional cost.

• Access Advisor using the REST API,

command line (CLI), PowerShell or
Azure portal.

Azure.com: aka.ms/advisor Documentation: aka.ms/docs/advisor

Azure Service Health
Alerts about active incidents and
upcoming maintenance:
• Service Health is available to Azure
subscribers at no additional cost.

• Track events in real time on mobile

devices or in your problem-
management system.

• Configurable cloud alerts notify you

about active and upcoming service
issues.

• Receive alerts via your preferred

channels, including email, SMS,
push notification, webhook and
popular IT service management
tools such as ServiceNow.

Azure.com: https://aka.ms/servicehealthalerts-acom Documentation: https://azure.microsoft.com/en-au/features/service-health

 Azure Lighthouse: Purpose-built for service providers
Deliver managed-services with greater automation, security, governance & management at-scale

Automate and scale Enable greater visibility, Build trust with just-enough
cloud management security and governance and just-in-time access

©Microsoft Corporation
Azure
 Azure Lighthouse secret sauce: Project customer resources into partner
environments with Azure delegated resource management

Customer resources,
Service provider projected
connects intocustomer
to each service provider tenant to be
cloud individually, managed
takes 4X theby authorized
amount service provider users
of time
Service provider can perform CRUD (Create, Read, Update, Delete) operations at scope; PIM license required only on service provider tenant

Service
provider tenant

Service provider
directory
Service provider
user group

Customer Customer-1 Customer-2 Customer-3 Customer-4

directory Subscription Subscription Resource group Resource group

Customer Customer Customer Customer

resources resources resources resources

©Microsoft Corporation
Azure
 Microsoft Commercial Marketplace
The customer experience

Customers select offers in Azure

Portal Service offer blade

How to: Create a Managed Service

offer in Microsoft Commercial
Marketplace

© Microsoft Corporation Azure

 Azure Lighthouse next steps: The immediate opportunity for
Service Providers

Reduce admin time and Stand out from the Generate incremental Enable security best
save time with rapid crowd with increased revenues with new practices without
service deployment security services offerings affecting budget

Onboard customers in
minutes using ARM or
Marketplace and save hours in
future management of clients
with Azure Lighthouse.
Use Azure Lighthouse’s existing Leverage Azure Lighthouse + Azure Lighthouse is free to
and new security features to Arc and Sentinel to build new use for customers and
protect your clients and services in hybrid partners
increase transparency. management and security.

Partner Admin Link included

©Microsoft Corporation
Azure
 Managing customers’ hybrid IT environments at scale is complex
Service providers want less complexity, more automation and comprehensive tooling to grow their business

Pains Motivators

Lack of skilled Optimize costs with Pace of change & Meeting compliance Reduced security Control and
IT resources rapid migration increased complexity requirements exposure transparency
Customer to cloud

Pains Motivators

Varied toolsets Inconsistent Inconsistent governance Unified & Automated CI/CD Simplified credential
are expensive onboarding processes across Azure and other comprehensive service delivery management with just-
environments management solution in-time access
Service Provider
 Get started today: Build, scale, and secure your services on Azure
with Azure Lighthouse

Make your voice heard Hone your skills Dive deeper Stay in the know
Help us improve - Submit your 100 & 200 level guided learning for Get step-by-step guides on MS Join the Azure Lighthouse partner
feedback for product enhancements securely scaling your managed Docs and helpful assets in the community and subscribe to the
and feature requests service practice Partner Resource Center Azure Partner Newsletter

aka.ms/AzureLighthouse
 Azure Lighthouse & Arc

WAF & CAF

Evolve your MSP offering

Drive customer evolution by leveraging
Microsoft tools, services and frameworks…
Azure Service Health

Azure Advisor
Next Steps?

Familiarize yourselves Consider how you're

with the tooling discussed managing your customers
today. today.

Apply todays insights & Immediate CTA: assess

update your MSP & migrate your customer
offering. off classic services.

Get skilled up on CAF & WAF.