Windows Server and SQL Server Migration to Microsoft

Azure Advanced Specialization

Program guide, audit checklist, and FAQ

Valid Jan 1, 2022 – June 30, 2022

Version 2.0.1
Program updates and announcements

Update Jan 1, 2022

Guidance and FAQ Updates

Update May 05, 2021

New Audit Fee Schedule

Please note the new audit fee schedule effective July 1, 2021

• For audits comprised of both Modules A and B, the audit fee is $3,000 USD
• For audits comprised of Module B alone (available for partners who previously passed Module A),
the fee is $2,000 USD

2
Contents

Windows Server and SQL Server Migration advanced specialization . ............. .3

How to apply.…………………………………………………………………………..….......4
NDAs for the audit ................................................................................................ 5
Payment terms and conditions ............................................................................ 5
Audit blueprint ...................................................................................................... 5
Audit roles .............................................................................................................. 6
Audit Process: High-level overview ..................................................................... 6
Audit Process: Details ........................................................................................... 7
Audit preparation best practices and resources ................................................ 9
Audit checklists ......................................................................................................11
Partner FAQ.......................................................................................................... 21

3
Windows Server and SQL Server Migration to Microsoft
Azure advanced specialization

Program overview

The Windows Server and SQL Server Migration to Microsoft Azure advanced specialization is designed for
partners to demonstrate their deep knowledge, extensive experience, and proven success in planning and
deploying Windows Server-based and SQL Server-based workloads to Azure cloud for their customers.
Such partners empower their customers to use Azure to realize the full breadth of Windows Server and
SQL Server to build transformative, secure workload solutions at enterprise scale.

The Windows Server and SQL Server Migration to Microsoft Azure advanced specialization allows partners
with an active Gold Cloud Platform competency to further differentiate their organizations, demonstrate
their capabilities, and build stronger connections with customers. Partners who meet the comprehensive
requirements to earn an advanced specialization, receive a customer-facing label they can display and a
business profile in Microsoft AppSource partner gallery.

In AppSource, access to specific Microsoft go-to-market programs is prioritized in customer searches to

help drive new business. Partners can also generate a certified letter from Microsoft that verifies the
advanced specialization that they have earned. For these reasons, this opportunity is available only to
partners that meet additional, stringent requirements.

This document defines the requirements to earn the Windows Server and SQL Server Migration to
Microsoft Azure advanced specialization. It also provides further requirements, guidelines, and an audit
checklist for the associated audit that is required to earn this advanced specialization.

Partners will receive a Pass or No Pass result upon completion of the audit process. A Pass result satisfies
the audit requirement for this advanced specialization for two (2) years. A No Pass result is generated
when a partner fails or withdraws from the audit. When a No Pass result is entered into Partner Center,
you will see your status as Audit Failed. Your status will reset after one week, allowing you to apply again.

Partners who have passed Azure Expert MSP V1.9 (Full and Progress) have satisfied the requirements for
Module A in all audit versions unless otherwise noted. When applying to subsequent Azure advanced
specializations, a previous audit Pass result will satisfy the requirements for Module A. The Pass result
must be within two (2) years and can only be applied to the same version of Module A.

How to apply

Only an MPN Account Administrator or a Global Administrator of an organization’s Microsoft partner

account can submit an application for the advanced specialization on behalf of the organization.
Partners with the appropriate role and access permissions can apply. To do so, they sign into their Partner
Center account. On the left pane, select Competencies, and then select Adv. Specialization.

4
Important: Take note of the audit effective dates and access the most current version from Partner Center.
(Audit checklists are updated twice a year). Partners audit on the version that is live on their audit date,
not the application date. Partners may apply for the audit only after all other program requirements have
been fully met. Partners must complete the audit within thirty (30) calendar days of the audit application,
and they must complete it against the then-current program requirements.

NDAs for the audit

Auditors comply with requests from partners to sign a direct NDA. All ISSI auditors are under a
nondisclosure agreement (NDA) with Microsoft. If a partner would like an NDA to be signed directly
between ISSI and the partner organization for purposes of the audit, one can be provided by the partner
during the audit scheduling process to ISSI. ISSI will sign and return it.

Payment terms and conditions

Pricing schedule
Module B Audit: $2,000 USD

Module A+B Audits: $3,000 USD

A Gap Review Meeting is included with each Module audit.

Payment terms

The cost of the audit is payable in full to the audit company and must be settled before the audit begins.
Failure to pay will result in cancellation of the audit.

Program status term

When a partner meets all prerequisite requirements shown in Partner Center and Microsoft receives a valid
Pass Report from the third-party audit company, the partner will be awarded the Windows Server and SQL
Server Migration advanced specialization for one (1) calendar year.

The status and the Windows Server and SQL Server Migration advanced specialization label can be used
only by the organization (determined by Partner Center MPN PGA ID account) and any associated locations
(determined by MPN PLA ID) that met all requirements and passed the audit. Any subsidiary or affiliated
organizations represented by separate Partner Center accounts (MPN PGA ID) may not advertise the status
or display the associated label.

Audit blueprint

Audits are evidence-based. During the audit, partners will be expected to present evidence they have
met the specific requirements on the checklist. This involves providing the auditor with access to live
demonstrations, documents, and SME personnel to demonstrate compliance with checklist requirements.

5
The audit checklist will be updated to stay current with technology and market changes, and the audit is
conducted by an independent, third-party auditor. The following is included in the audit blueprint:

1. Audit Roles
2. Audit Process: High level overview
3. Audit Process: Details
4. Audit Best practices and resources

Audit roles
Role of the auditor

The auditor reviews submitted evidence and objectively assesses whether the evidence provided by the
partner satisfies the audit checklist requirements.

The auditor selects and evaluates evidence, based on samples of the information available from live
systems. The appropriate use of such sampling is closely related to the confidence that can be placed in
the audit conclusions. All ISSI auditors are under a non-disclosure agreement (NDA) with Microsoft.
Auditors will also comply with requests from partners to sign a direct NDA.

Role of the partner

The partner must provide objective evidence that satisfies the auditor for all checklist items. It is the
responsibility of the partner to have reviewed all checklist items prior to the audit, to have collated all
necessary documentation and evidence, and to have ensured that the right subject matter experts are
available to discuss and show systems, as appropriate. All audit evidence must be reproducible and
verifiable.

Role of the Microsoft Partner Development Manager

For partners that have an assigned Microsoft Partner Development Manager (PDM), the PDM is responsible
for ensuring that the partner fully understands the requirements prior to applying for the audit. The PDM
may attend the optional consulting engagements that ISSI offers, but the PDM and other Microsoft FTEs
may not attend the audit.

Audit Process: High-level overview

Step Action Responsibility

1 Review: Specialization requirements in Partner Center. Review audit Partner

checklists in the specialization and begin to prepare needed evidence with
personnel for an evidence-based audit. Recommended: Before you apply,
review the specific audit checklist thoroughly and confirm SME personnel.

6
 2 Meet the prerequisites and apply for the audit: In the initial application Partner
phase, applications are submitted in two (2) stages:
1. Prerequisite requirements (see Partner Center for details)
2. Audit
Do not start the application process unless you are ready to undertake the
audit. Assess your firm’s ability to complete the audit, including
considerations for readiness, employee availability, and holidays.

3 Validate: The partner meets all requirements prior to audit. Microsoft

4 Confirmed by Microsoft: Microsoft confirms to the third-party audit Microsoft

company that the partner is eligible for audit.
5 Schedule with partner: The auditor will schedule within two (2) business Auditor (with
days. partner)
6 Conduct the audit: Within thirty (30) calendar days of the approval for Auditor
audit.
7 Provide a Gap Report: If applicable, to the partner within two (2) business Auditor
days of the completed audit, listing any Open Action Items.*

8 Acknowledge Gap Report receipt and schedule meeting: Partner

Within two (2) business days of receiving the Gap Report, the
partner acknowledges receipt of the report and schedules a Gap
Review Meeting. Partners can begin immediate remediation of
open items.
9 Complete the meeting: Within fifteen (15) calendar days of Auditor (with
receiving the Gap Report, the partner schedules and completes the partner)
Gap Review Meeting with the auditor to provide evidence and
address any Open Action Items.*
10 Issue Final Report: To the partner within five (5) business days. Auditor
Notify Microsoft of audit Pass or No Pass result.

11 Notify the partner: About program status within two (2) business days. Microsoft

* These steps will be skipped if the partner has no Open Action Items after the audit.

Audit Process: Details

Microsoft uses an independent, third-party audit company, Information Security Systems International,
LLC (ISSI), to schedule and conduct advanced specialization audits. After the audit date has been
confirmed, ISSI will provide an agenda to the partner. The duration of an audit is four (4) hours for
Module B workloads and eight (8) hours for Module A+B audits combined, depending upon the scope of
the audit.
During the audit, the partner must provide access to the appropriate personnel who can discuss and
disclose evidence that demonstrates compliance with program requirements. We highly recommend that
subject matter experts for each section attend as well as a person who is familiar with the entire audit.

7
 On the day of the audit, the partner must be prepared to provide the auditor with access to live
demonstrations, documents, and personnel, as necessary to demonstrate compliance with the
requirements. During the audit, the auditor will seek to verify that the partner’s evidence has addressed
all required audit checklist items satisfactorily.

A note on audit checklist effective dates: Partners are audited against the checklist items that are active
on the date of their remote audit, not the date they apply. Audits are updated twice annually. The
partner application or renewal date has no bearing on the version of the checklist that is used for the
audit.

The audit can produce either of two (2) outcomes:

1. The partner passes the audit.

• The auditor will present a brief synopsis of the audit. This will include identifying observed strengths
and opportunities for improvement.
• The auditor will provide a Final Report to the partner.
• The auditor will notify Microsoft.

2. The partner does not satisfy all checklist items during the audit.
• The auditor will present a brief synopsis of the audit at the end of the day, including observed
strengths and Open Action Items, as outlined in the Gap Report, within two (2) business days.
• The partner will acknowledge receipt of the Gap Report within two (2) business days.
• The partner will move into the Gap Review phase and schedule their Gap Review Meeting within fifteen
(15) calendar days.

The Gap Review

If the partner does not, to the auditor’s satisfaction, provide evidence that meets the required scores
across all audit categories during the audit, the partner will move into a Gap Review. A Gap Review is
part of the audit and completes the process.
Within two (2) business days after the audit, the partner will receive a Gap Report, which details any
Open Action Items and the outstanding required evidence. It is suggested to begin remediation on any
open action items as soon as possible following the audit.

The partner then has two (2) business days to acknowledge receipt of the Gap Report and schedule a
Gap Review Meeting. The Gap Review Meeting is conducted with the auditor over the partner’s virtual
conference platform of choice. The meeting must take place within fifteen (15) calendar days of when the
Gap Report was sent, and it may last no longer than one (1) hour. During the Gap Review Meeting the
partner must present evidence that addresses any and all Open Action Items.

The Gap Review Meeting can produce either of two (2) outcomes:

1. The partner resolves all Open Action Items.

• The auditor confirms that the partner has provided the required evidence.
• The auditor provides a Final Report to the partner.
• The auditor notifies Microsoft about the outcome (subject to Auditor Terms and Conditions).

8
2. The partner does not resolve all Open Action Items.
• The auditor presents a brief synopsis of the audit, including missed items.
• The partner receives a Final Report that details the missed items.
• The auditor notifies Microsoft about the outcome (subject to Auditor Terms and Conditions).

If the partner is still unable to provide satisfactory evidence to the auditor during their Gap Review
Meeting, the partner will be deemed to have failed the audit. Partners that still want to earn this advanced
specialization will need to begin the application process again.

Completion of the audit

The audit process concludes when ISSI issues the Final Report after the audit or after the Gap Review.
Partners will be awarded a Pass or No Pass result upon completion of the audit process, including if they
withdraw from the audit process.

Audit preparation best practices and resources

Partners should ensure that the audit checklist has been thoroughly read in advance of the audit

• Partners should ensure that all partner stakeholders involved have a copy of the audit checklist and
that a stakeholder who knows the entire process is available for the duration of the audit
• Partners should confirm that they have live access granted and files and tools are readily available
during the audit exhibits

Stakeholder SME attendance in the audit

Stakeholders who can best address the relevant section should be available for the audit. However,
please make sure that a stakeholder who knows the entire process is available for the duration of the
audit.

Auditors often probe for more information

The auditor probes for more information to ensure that mature and repeatable processes are in place
with the partner and that they are establish, effective, and efficient. The auditor is looking to see how a
document was created, where it is located, and what source materials were used to create the document.
By probing for more information, the auditor evaluates and validates that the partner is operating at an
advanced level. This can only be done by questioning during the audit. This approach is explained to the
partner during the opening meeting.

Acceptable evidence: Excerpts, exhibit file formats and use of PowerPoints

PowerPoints are a common and accepted format for presenting a high-level overview of a partner’s
systems. However, please also be prepared to present live demonstrations from source files so that the
auditor may confirm that the systems in place are mature and effective. Excerpts can be used to
communicate the high-level overview but are not acceptable evidence, source documents must be
presented.

9
Additional resources: Optional ISSI consulting offers

ISSI provides optional extensive, in-depth consulting engagements to help partners prepare for their
Azure advanced specialization audit. Partners can work directly with ISSI to schedule this remote session
(via online web conference). For more information about this type of in-depth engagement, see Azure
Advanced Specializations - Consulting Offer.

Alternatively, partners can participate in an optional, one (1)-hour, live Audit Preparation Overview
session provided by ISSI. This session provides a high-level overview of key aspects of the advanced
specialization audit process. The session includes a discussion of the checklist requirements along with
best practices to help partners prepare for the audit. Partners work directly with ISSI to schedule this
remote session (via online web conference). For more information about this session, see Azure
Advanced Specializations - Audit Preparation Overview.

To ensure objectivity, audits are conducted by a different ISSI auditor than the one that is engaged for
consulting. Consulting engagements can be scheduled at any time using the partner’s preferred
conferencing platform.

* Please note that there is a cost associated with the consulting and audit preparations services. See Payment Terms
and Conditions.

10
Audit checklists

The Windows Server and SQL Server Migration to Microsoft Azure advanced specialization checklist contains
two (2) modules, Module A: Cloud Foundation and Module B: The Windows Server and SQL Server Migration
to Microsoft Azure advanced specialization workload. Module A, The Cloud Foundation module evaluates the
use of a consistent methodology and process for Azure adoption that is aligned with customers’ expected
outcomes, spanning the entire cloud adoption lifecycle.

Module B, The Windows Server and SQL Server Migration to Microsoft Azure advanced specialization workload
module validates that the partner has adopted robust processes to ensure customer success across all phases
of deploying Windows Server and SQL Server Migration solutions, from the assessment phase to design, pilot,
implementation, and post-implementation phases.

Review the following audit checklist tables for more details about each control phase and to learn how the
partner will be evaluated for an audit. The same customers may be used for Module A & B. The estimated
length of both modules together is eight (8) hours.

Module A: Cloud Foundation

1. Strategy
2. Plan
3. Environment readiness and Azure landing zone
4. Governance
5. Manage

Module B: Windows Server and SQL Server Migration to Microsoft Azure workload

1. Assess
2. Design
3. Deployment
4. Review and release for operations

To pass the audit, the partner must complete all audit checklist items.

11
Module A: Cloud Foundation is required for multiple Azure advance specializations. To complete
Module A: Cloud Foundation, the partner needs to pass all controls in Module A by providing the
specified evidence. Alternatively, the partner may present evidence of a previous pass result from
Module A or from another advanced specialization audit conducted on V2.0 or later.

Module B: The Windows Server and SQL Server Migration to Microsoft Azure advanced specialization
workload. Each control has one (1) or more requirements and required evidence the partner must
provide for the auditor. Both the requirements and the required evidence are defined in the following
tables. For some controls, a reference customer or customer evidence is the documentation requested.
Unless otherwise stated, the partner must show at least three (3) unique customers with deployments
completed within the last twelve (12) months. Please note some checklists call for four (4) customer
examples.

The partner can use the same customer across audit checklist controls, or they can use a different
customer. For audit evidence relating to customer engagements, the partner can use a customer case
study and reference it multiple times. The same or different customers can be used for Modules A & B
if they demonstrate requirements.

Module A: Cloud Foundation

1.0 Strategy

The partner must have a defined approach for helping their customer evaluate and define a cloud adoption
strategy beyond an individual asset (app, VM, or data).

Requirement
1.1 The partner must have a process that captures the data-driven business strategies being used to
guide customer decisions. Their process should include, at minimum, the following:

• A strategy review for capturing the customer’s business needs and/or problems the
customer is trying to solve.

Required evidence:
A report, presentation, or document that captures strategic inputs and decisions for two (2) unique
customers, with projects completed in the past twelve (12) months that are aligned with the process.
For an example, see the Strategy and plan template in the Cloud Adoption Framework for
Azure.

2.0 Plan

The partner must have a consistent approach to planning for cloud adoption that is based on the strategy outlined
in the preceding section.

Requirement

12
2.1 The partner must have a process and approach for planning and tracking the completion of cloud
adoption projects. For an example of a cloud adoption plan, see the Azure DevOps Demo Generator
for the Cloud Adoption Framework.

Required evidence:
The partner must provide evidence of their capability with examples of two (2) unique
customers,with projects that were completed in the past twelve (12) months. Acceptable
evidence must include at least one (1) of the following:

• Cloud Adoption Plan Generator output

• Azure DevOps backlog
• Any other tools for project planning and tracking

3.0 Environment readiness and Azure landing zone

The partner must be able to demonstrate that the following design areas are addressed through their approach to
landing zone implementation.

Requirement
3.1 Repeatable deployment
The partner must demonstrate adherence to Azure landing zone design areas through a
repeatable deployment. The deployment should configure, at minimum, the following identity,
network, and resource organization attributes:

• Identity
o Adoption of identity management solutions, such as Azure Active Directory or
equivalent

• Networking architecture design (topology)

o Adherence to the guidance in Review your network options
o Application of hybrid architectures that use Azure ExpressRoute, VPN Gateway, or
equivalent services for connecting local datacenters to Azure

• Resource organization
o Implementation of tagging and naming standards during the project

The partner should be able to demonstrate which of the following deployment velocity
approaches they use when they deploy Azure landing zones:

1. Start small and expand: Azure landing zone does not deploy governance or
operationsconfigurations, which are addressed later in the implementation.

13
 2. Enterprise-scale: Azure landing zones implement a standard approach to
theconfiguration of governance and operations tools prior to
implementation.

3. Alternative approach: If the partner follows a proprietary approach or a mixture of

thetwo approaches above, they must clearly articulate their approach to
environment configuration.

Required evidence:
The partner must provide evidence of a repeatable deployment they use to create landing zones
that they have deployed to two (2) unique customer environments by using Azure Blueprints,
ARM templates, Terraform modules, or equivalent tools to automatically deploy the
environment configuration.

The provided template can be pulled directly from the provided implementation options, or it
can be based on the partner’s own IP. In either case, the script must demonstrate the
configuration of the identity, network, and resource organization, as described earlier.

4.0 Governance

The partner must demonstrate their customer’s role in governing cloud-based solutions and the Azure tools they
use to facilitate any government requirements their customer might have today or in the future.

Requirement
4.1 Governance tooling
The partner must demonstrate the ability to deploy the required governance tools for two
unique customer projects.

Required evidence:
The partner must demonstrate the use of Azure Policy or equivalent tool to provide controls to
govern the environment for two (2) unique customers with projects that were completed in the
past twelve (12) months.

5.0 Manage

The partner must demonstrate that they have set up their customer for operational success after the deployment is
completed. All partners have a role in setting up operations management, even if they do not provide long-term
managed services.

Requirement

5.1 Operations management tooling

The partner must demonstrate the use of Azure products or equivalent to help their customer and/or
managed service provider operate the environment after deployment.

Required evidence:
The partner must demonstrate the deployment of at least one of the following Azure products or third-
party equivalents: Azure Monitor, Azure Security Center, Azure Automation, or Azure Backup/Site
Recovery, for two (2) unique customers with projects that were completed in the past twelve (12) months.

14
Module B: Windows Server and SQL Server Migration to Azure
workload

1.0 Assess

The partner must have a consistent approach for assessing customer requirements for the workload.

Requirement

1.1 Workload assessment

The partner must demonstrate how they assess each workload prior to migration to ensure that adequate
pre-migration or pre-deployment planning and sizing were performed.

The assessment must include mapping that shows the dependencies upstream from the resources that will
be migrated. It must also show:

• The data volumes and database sizes to be migrated.

• The migration timeline and approach.
• The migration risk assessment.
• Backup and disaster recovery for existing workloads.
• Licensing and cost management requirements.
• Documentation of the customer’s existing identity implementation on Azure, gaps identification,
and best practices recommendations.

Required evidence:
The partner should provide relevant design documents showing that the preceding items were reviewed for
at least three (3) unique customers with Windows Server and SQL Server migration projects that were
completed within the past twelve (12) months. The partner must show that all assessment details were
considered for those customers. Assessments may be done manually or through an industry-accepted
assessment tool.

Accepted documentation: Output from assessment tools, such as Azure Migrate, Movere, or other similar
third-party tooling reports, assessment checklists, templates, questionnaires, or project plans.

2.0 Design

The partner has robust methodologies for designing the workload.

15
Requirement

2.1 Solution design

The partner must provide solution designs that show a consistent approach to addressing customer
requirements that were captured from the assessment phase.

Completed migration projects must meet at least one of the following scenarios:

• Migration of Windows Server-based applications to Azure

• Migration of Microsoft SQL databases to Azure

The solution design must show:

• A migration design or strategy that outlines which applications, databases, or database auxiliary
components (reporting service, integration service) are in scope for the migration.

• An outline of the migration method (rehost, refactor, or replatform) to be used for the application,
database, database auxiliary components, and so on. It should show how the design addresses the
workload dependencies that were demonstrated in the assessment, with appropriate mitigations.

• The migration risk mitigation.

• The high-level migration sequence and estimated time to finish the migration.

• The validation of the successful migration completion.

• Azure landing zone: The environment that supports the reference deployments should address
each of the following required design areas. If an item is not relevant, the partner must document
the customer’s decision to deviate from applying best practices.

o Implementing Identity & Access Management (IAM) and role-based access control (RBAC),
data sovereignty and encryption, application security, and auditing.
o Establishing a hub and spoke architecture or retrofitting the existing deployment to separate
out the network components of a hub for optimal performance and security.
o Showing resource and perimeter security, such as bastion hosts, network security groups
and/or Azure Firewall, and/or virtual security and routing appliances with appropriate
monitoring.
o Using security products, such as Azure security services, Microsoft 365 security, or other
security solutions, to secure access to the data.
o Using governance tooling to support cost optimization across the environment. After
estimating the initial cost, setting budgets and alerts at different scopes to proactively
monitor the cost.
o Using backup and recovery solutions to ensure data retention.
o Meeting requirements for government regulatory compliance in the new environment, such
as GDPR and HIPAA, and implementing them through multiple datacenter regions, as
needed.
o Implementing a monitoring solution to provide proactive remediation for the Azure
environment, to integrate with the customer's existing monitoring tooling, if appropriate.
o Showing that visualization and alerting considerations for solutions are in place, where
appropriate.

16
 Required evidence:
The partner must provide relevant solution design documents that address all the preceding points for at
least three (3) unique customers with migration projects that were completed within the past twelve
(12) months.

Acceptable documentation: Project plan, functional specifications, solution design document, architectural
diagram, automated tooling reports, and physical and logical diagrams.
2.2 Azure Well-Architected Review of workloads
The partner must demonstrate usage of the Azure Well-Architected Review on migrated applications. The
Azure Well-Architected Review is designed to help partners evaluate your customers' workloads against the
latest set of industry best practices. It provides actionable guidance to design and improve your customers'
workloads.

The Review can be used to evaluate each workload against the pillars of the Azure Well-Architected
Framework that matter to that workload.

Required evidence:
The partner must provide exported results from the completed Microsoft Well Architected Review using the
assessments in the Well Architected Reviews for at least three (3) migrated Windows Server or Microsoft
SQL workloads that were completed within the last twelve (12) months, indicating the customer's name.

The three (3) workloads can come from one or more customers.

3.0 Deployment

The partner has robust methodologies for deploying the workload.

Requirement

3.1 Infrastructure migration

The partner must provide evidence of their ability to implement an infrastructure migration of Windows
Server to a production environment based on customer approved designs, from one of the following Azure
scenarios:

• Move the application from an on-premises Windows Server to Azure infrastructure as a service
(IaaS).
• Move the application that is running on Windows Server from another public cloud platform to
Azure IaaS.

Required evidence:
The partner must provide documentation for three (3) unique customers with infrastructure migrations of
Windows Server to production environments that were completed within the past twelve (12) months.

To cover the entire sequence of the project, including design and production deployment, the
documentation must include at least two (2) of the following items:

• Signed statements of work (SOWs) for all projects

• Solution design documents for all projects
• The project plan and migration and deployment sequence
• Architecture diagrams
• High-level designs (HLDs) and low-level designs (LLDs)
• As-built documentation

17
3.2 Database migration
The partner must provide evidence of their ability to implement a SQL Server Database migration to a
production environment, based on customer-approved designs for two unique customers for each of the
following migration scenarios:

• Rehosting from SQL Server on-premises or from another public cloud to SQL IaaS on Azure.
• Replatforming from SQL Server on-premises or from another public cloud to SQL platform as a
service (PaaS) on Azure (SQL Database or SQL Managed Instance).

Required evidence:
The partner must provide documentation for each unique customer’s database migrations that align with
the solution design requirements in section 2. Each of the four (4) database migration projects must have
been implemented within the past twelve (12) months.

To cover the entire sequence of the project, including design and production deployment, the
documentation must include at least two (2) of the following items:

• Signed SOWs for all projects

• Solution design documents for all projects
• The project plan and migration and deployment sequence
• Architecture diagrams
• HLDs and LLDs
• As-built documentation

3.3 Migration tools

The partner must demonstrate the specific products, tools, or scripts that were used for the assessment and
migration of workloads. The demonstration must be done in a customer-facing manner.

Required evidence:
Partners must prove experience with at least one (1) of the following options through a demonstration of
tools (A, B, or C):

A. Show experience with using native Azure migration tools by providing a step-by-step demonstration
that they can effectively use at least four (4) of the following tools:

• Azure Migrate Server Assessment for VMware and Hyper-V

• Data Migration Assistant (DMA)
• SQL Server Migration Assistant (SSMA)
• Azure Migrate Server Migration VMware and Hyper-V (use of Azure Site Recovery is also
accepted)
• Azure Database Migration Service
• Storage Migration Service
B. Show experience with third-party tools that integrate with Azure Migrate by demonstrating a
customer project where assessment data is available from Azure Migrate or available to them offline and
they perform the migration by using third-party tooling.

C. Show experience with all other third-party tools by referencing the tools that they used in a project
plan for successfully migrating a customer to Azure, or by providing snapshots of results or an output
file from the tools that they used. Tools may include but are not limited to:

18
 • StratoZone
• CloudEndure
• Carbonite
• PlateSpin

3.4 Automated deployment and provisioning tools

The partner must demonstrate specific products, tools, or scripts that they used for automated provisioning
and deprovisioning of infrastructure, including tools for continuous integration and continuous delivery
(CI/CD).

Required evidence:
Demonstrations of products, tools, or scripts used for:

• Automated deployment, including creation of workload deployment templates.

• Cloud service provisioning and deprovisioning, including viewing of service template, packages, or
runbooks that were used in the deployment of customers’ Azure environments.
• Automation of routine operations, or automated scale-out.

4.0 Review and release for operations

The partner has robust methodologies for transitioning the workload.

Requirement
4.1 Service validation and testing
The partner must validate the deployment, including:

• Their documented process and approach to testing and evaluating the performance of all
applications against customers’ expectations and Azure best practices.
• Their documented process and approach to evaluating and improving architectural best practices
to remediate issues with migrated platforms or workloads that do not meet performance or cost
expectations.

Required evidence:
Documentation of a testing, validation, and performance evaluation that addresses the preceding points
for three (3) unique customers. The documentation must indicate that the implemented solution meets
customer expectations, and it must include a sign-off from the customer.

The Windows Server and SQL Server migration projects must have been completed within the past twelve
(12) months. These projects can be the same as the projects evidenced in Control 3.0.

4.2 Post-deployment documentation

The partner must provide post-deployment operational documentation to show that their customers are
successfully using the new service on Azure.

• Demonstrate how the partner’s documents, decisions, architectural designs, and procedures were
implemented.
• Demonstrate standard operating procedures for the business-as-usual operations team that

19
 describe “how-to” scenarios.

Required evidence:
Documentation showing the preceding points for three (3) unique customers with completed Windows
Serverand SQL Server migration projects. These projects can be the same as the projects evidenced earlier.

20
Partner FAQ
Definition of a Customer

A customer is a company which has direct contractual relationship with the partner and is not
affiliated with the partner. Each customer tenant ID (TPID) attached to the partner by DPOR, CSP
or PAL is counted as one customer. A customer can be different companies, or different
departments within the same company, represented by different TPIDs, but the projects must
have different stakeholders. Internal projects are not accepted as customer evidence for advanced
specializations. The customer’s project must be executed by the partner applying for the
accreditation program. Microsoft will not accept customer evidence from a company not included
in the applying MPN PGA ID (Vorg).

Who can participate in the program?

The program is open to any members of the Microsoft Partner Network program who can meet
the program requirements and pass the audit.

Can a partner have more than one advanced specialization?

Yes, if you qualify, you can earn as many advanced specializations as you choose. Earning
additional advanced specializations will increase your visibility to customers in the Partner Finder
tool.

Is a partner’s advanced specialization global or local?

It depends on how your company has set up your account in Partner Center. If your company has
one global account (Partner Center MPN PGA ID), your advanced specialization is assessed and
awarded at the global level. If you have set up multiple Partner Center accounts (MPN PGA ID) to
represent different divisions, countries, subsidiaries etc., only the account that earned the
advanced specialization will be awarded it.

Is there a cost to participate in the audit?

Microsoft does not charge a program fee. However, there are direct costs associated with the
following requirements:

• Gold Cloud competency

• Microsoft and third-party certifications

• Audit

In addition, there are indirect costs associated with preparation for the audit.

21
How much time and how many resources (people) do we need to commit to preparing to
meet the audit requirements?

The amount of time it takes to meet all requirements and pass the audit varies greatly. It depends
on how many of your current employees already have the required Azure skills, whether they have
documented customer wins, and how you document your people, technology, and processes.

How long do the actual audits take?

The remote audit will be either half day or a full day, based on the scope of the modules being
audited. Module A is generally four (4) hours and Module A+B is generally eight (8) hours to
complete. However, as mentioned above, significant preparation is required to be audit-ready.
We recommend that you read the audit checklist thoroughly and, to streamline your preparation,
and consider the consulting and audit preparation overview offered by ISSI.

How much does the audit cost?

The audit fee for Module A or Module B standalone is $2,000 USD, the audit fee for Modules A+B
combined is $3,000 USD. The fee is paid to the third-party independent auditor. The audit fee
must be paid in full before the audit is completed.

How do we apply to the program?

You can apply by signing into your Partner Center account, then navigating to your Partner
Center dashboard. Select Competencies > advanced specializations from the Partner Center
navigation menu, followed by the specific advanced specialization.

When should we apply to the program?

Do not apply for the program until you have met all the program requirements prior to the audit.
Be sure you have thoroughly reviewed the audit requirements and are confident you can satisfy
them.

What checklist version will we be audited on?

Take note of the active dates for the audit checklist. Partners are audited against the checklist
items that are active on the date of their remote audit. The original application date has no
bearing on the version of the checklist that is used for the audit.

In which languages are the audits conducted?

These are the current audit languages:

• English

• Portuguese

• Spanish

• French

• German

22
• Italian

• Serbian

• Croatian

• Russian

• Hebrew

• Mandarin

• Japanese

• Korean

• Arabic

What languages can we provide evidence and documentation in during the audit?

ISSI will make every effort to support the partners’ specific language need. In instances where this
is not possible, the working language for the audit will be English. Partners may present evidence
and documentation in their local language. It is not required for the partner to translate their
documentation into English for the purposes of the audit.

What types of evidence should be used as examples for the audit?

The evidence should relate to the project and be signed-off by the customer no earlier than 24
months before the audit.

What is the definition of a project for audit evidence?

A project is a paid endeavor resulting in a customer solution used in production. Projects should
be complete when presented as evidence. In the case where a project is complex and prolonged;
it can be enough to have completed the POC as part of a project stage and to demonstrate that
stage as evidence. Pilots and Proof of Concept (PoC) by themselves do not qualify as projects,
however these may be required as part of a project for evidence.

How is the audit scored?

The partner score for the audit checklist is based on the checklist controls. To pass the audit,
partners must complete all sections in each control area. They must provide adequate evidence to
demonstrate the existence, effectiveness, and efficiency of their processes, policies, procedures,
and tooling against each checklist item.

What if I meet only some of the requirements?

Because this is an advanced specialization audit for an opportunity for partners to truly
differentiate your business, we expect partners to demonstrate that they meet each of the
controls by providing evidence that satisfies all requirements.

23
What happens if I don’t pass the audit outright?

At the conclusion of the audit process, the auditor will issue a Final Report to the partner and
notify Microsoft of the pass or no pass result. Partners that receive a no pass result may reapply
for the advanced specialization in six (6) months.

Partners that withdraw from the audit process without completing the audit may submit a ticket
through Partner Center support to request that their status be reset to “Not Enrolled,” which
enables them to reapply.

Who conducts the audit?

The audit is carried out on behalf of Microsoft by an independent, third-party auditor, appointed
by Microsoft. The audit company is Information Security Systems International (ISSI).

Can I contact the auditor to schedule the audit before I apply or as soon as I apply?

No. The audit company, ISSI, cannot schedule your audit until it receives an official notification
from Microsoft. Microsoft will issue the notification only after you have shown that you meet all
program requirements and you have applied for an audit by selecting “schedule audit” from the
Partner Center dashboard. ISSI will reach out to you to begin the scheduling process within one
(1) to two (2) business days.

What is the difference between the audit and the consulting and audit preparation?

Consulting and the Audit Preparation Overview are optional resources and conducted by the
third-party audit company, ISSI. The purpose is to help partners prepare for the Azure advanced
specialization audit.

To ensure objectivity, audit preparation consulting is conducted by someone other than your
assigned remote auditor. You can schedule consulting engagements at any time by using your
preferred conferencing platform.

Are the consulting and audit preparation mandatory?

No, the consulting and Audit Preparation Overview are optional. However, we do recommend
that you opt for the consulting and audit preparation, because it can help ensure that you are
more prepared for the audit.

What is an advanced specialization?

An advanced specialization is an extensive validation of a partner’s capability to deliver high-

fidelity services in a specific solution area. Advanced specializations are customer-facing labels
displayed on a partner’s business profile. They are used in our customer referral engine to allow
partners to showcase their differentiated capabilities in a specific solution area. To earn an
advanced specialization, partners must first hold an aligned active Gold competency.

How is an advanced specialization different from a competency?

24
A competency measures a partner’s broad technical capability in a Microsoft product or
technology. An advanced specialization measures more in-depth capabilities in a specific solution
area, such as Analytics on Microsoft Azure.

Does a partner need a competency to earn an advanced specialization?

Yes. Advanced specializations can be earned only by partners with an active Gold Cloud
competency. For example, to earn the Analytics on Microsoft Azure advanced specialization,
partners must first have an active Gold Cloud competency and then pass the specialization audit
in Analytics on Azure.

What advanced specializations are available to partners?

Certain competencies have different advanced specializations available to them. For details on all
available advanced specializations, go to the advanced specializations site.

Why would a partner want to get an advanced specialization?

With an advanced specialization, partners can differentiate their capabilities to customers that are
looking for partners to help them with a business need. Partners with an advanced specialization
are listed first in Partner Finder, a Microsoft-owned, customer-facing tool. Advanced
specializations are also indicated on a partner’s business profile alongside their competency
status.

What are the benefits of an advanced specialization?

Partners with an advanced specialization are listed first in Partner Finder, a Microsoft-owned,
customer-facing tool. Advanced specializations are also indicated on a partner’s business profile
alongside their competency status.

How does a partner earn an advanced specialization?

Each advanced specialization has a set of requirements that a partner must meet. The criteria
depend on the advanced specialization the partner is seeking, but they can include performance
requirements, exams, customer evidence, and third-party certification, among others. For detailed
criteria for individual advanced specializations, go to your Partner Center dashboard. Advanced
specializations are not available in PMC.

Is there a cost associated with attaining an advanced specialization?

Microsoft does not charge a program fee. However, there are direct costs associated with the
following requirements:

• An active Gold Cloud competency

• Microsoft certifications
• The audit, optional ISSI consulting and audit preparation, and third-party certifications

25
In addition, there are indirect costs associated with preparation for the audit, including audit
preparation hours.

How long do partners keep their advanced specialization?

Your advanced specialization will remain in place for one (1) year, but it requires that you
maintain an active aligned Gold competency defined in the advanced specialization requirements.
If you do not maintain your active Gold competency, you will lose your advanced specialization
status. On your renewal date, you will need to meet the then-current requirements. Requirements
may evolve over time.

When and how do partners renew the advanced specialization?

Partners renew their advanced specialization on their anniversary date. See the specific
requirements in Partner Center. Partners must also maintain an active, aligned Gold
competency.

Do partners need to requalify for the advanced specialization after a specific period of
time?

Yes. Partners must meet the requirements each year. A partner firm should expect the
requirements to evolve year over year, to best meet the needs of customers. Partners will be
expected to undergo an annual audit as part of the renewal process.

What happens to the advanced specialization if a partner does not renew their associated
Gold competency?

To maintain an advanced specialization, partners must keep their active, aligned Gold competency
status at all times.

How will my customer know whether my company has an advanced specialization?

Your advanced specialization will be listed on your Business Profile.

What can partners tell customers about advanced specializations?

An advanced specialization is a customer-facing label on your Business Profile. It is not a brand,

and it does not have a badge associated with it. However, you can tell your customers which
advanced specializations you have earned. They can validate by reviewing your Business Profile in
the Partner Finder tool.

What if my company has an endorsement now?

As advanced specializations go live, they replace endorsements on the customer-facing profile.

Each advanced specialization has published requirements for partners to meet to earn them.

26
Can a company have both an endorsement and an advanced specialization on its profile?

No. As advanced specializations go live, they replace endorsements on the customer-facing

Partner Profile.

Does a partner get a badge to use externally in their marketing to differentiate their
advanced specialization?

Advanced specializations do not have a badge or a logo. An advanced specialization is a label that
is displayed on the partner’s customer-facing Partner Profile.

Other questions on the program?

If you have questions that we have not answered in this document, please go to Partner Center
support to create a ticket with our Frontline team.

27