SAP on Azure Partners: Specialization Rules, Cloud Accelerate Factory and FY27 Funding

• The SAP on Microsoft Azure Specialization
• Turning SAP modernization into "AI-led growth"
• Using the Cloud Accelerate Factory (CAF) to speed up customer transformation projects

That description is all that's publicly available about the call. There's no transcript, speaker list, timestamps or slide deck. So this piece doesn't say what the presenters announced or recommended. Instead, it explains what Microsoft's published documentation says about each topic, so partners and the IT teams who hire them can check the details for themselves.

Why a Partner Call Matters to IT Pros​

SAP landscapes are among the most complex, expensive and politically sensitive systems an enterprise runs. They handle finance, supply chain and HR, often all at once. When a company moves SAP to Azure, a Microsoft partner usually does much of the work. The rules governing those partners affect who a customer can hire, what help Microsoft adds for free and how a project gets funded.

If you're an IT decision-maker, these programs are worth understanding even if you never log in to Partner Center. They shape the proposals that land on your desk.

Section summary: The call is a partner-program update. Its three topics matter for anyone buying or delivering SAP-on-Azure work.

The SAP on Microsoft Azure Specialization: What It Takes​

Microsoft's current Partner Center documentation lists SAP on Microsoft Azure as an Azure specialization with four sets of requirements:

The eligible ACR list covers SAP workload services such as MS-series virtual machines and cloud services, SAP HANA on Azure Large Instances, and some SAP Cloud Platform services.

These requirements were eased earlier this year. In January 2026, Microsoft's specialization blog described updated SAP on Microsoft Azure specialization requirements, including reduced ACR and direct skilling validation in Partner Center. The post said partners can validate required Microsoft learning coursework directly within Partner Center, removing the need to do so in the third-party audit for this specialization. In practice, the learning-path option is a real alternative to the exam for partners that can't yet put three certified people forward.

For teams choosing the certification route, Microsoft describes the credential (exam AZ-120) as intermediate-level. It's aimed at architects and engineers who design and run SAP landscapes on Azure, covering migration, infrastructure design, high availability and disaster recovery, and ongoing maintenance. The page says the exam lasts 100 minutes, the certification renews every 12 months, and Microsoft strongly recommends holding Azure Administrator Associate first. It was last updated April 17, 2026.

Why the badge matters beyond marketing​

In Microsoft's partner programs, specializations often decide who can access funding. Microsoft's SAP Partner Community FAQ on the FY26 incentives stated that partners must be enrolled in the Microsoft AI Cloud Partner Program and have achieved the SAP on Microsoft Azure Advanced Specialization. Enrollment in the Microsoft Commerce Incentives (MCI) program is also required. The same FAQ said public sector deals are generally excluded. Extremely large strategic accounts may use custom funding instead.

A caution: that FAQ covered Microsoft's fiscal year 2026, which ended in June. Partners should check current FY27 terms rather than assume the old rules still apply.

Section summary: The specialization requires an Infrastructure designation, $7,500 in SAP-related ACR from three customers over three months, three skilled staff and an audit. It also works as a gate to SAP funding.

Cloud Accelerate Factory: Free Help, With Conditions​

CAF is the most practical of the three topics. Microsoft describes it as zero-cost, Microsoft-led deployment assistance across more than 30 Azure services. A partner-focused explainer from Digital Innovation summarizes the model: CAF is designed to complement partner delivery services by allowing partners to focus on solving complex challenges while Microsoft handles predictable, repeatable tasks.

The main change came in a Microsoft Partner Center announcement dated July 8, 2026. CAF used to be available only through the Azure Migrate and Modernize and Azure Innovate offerings. The announcement widened access to partners holding eligible Azure specializations, and SAP on Microsoft Azure is one of them. Some partners in selected Security and other specialization engagements also qualify.

The announcement sets out two routes:

1. Partner-nominated engagements: partners can use existing incentives and CAF together on the same engagement.
2. ECIF or field-nominated engagements: partners complete a one-time activation, then submit eligible engagements directly.

This is how incentives stack. Microsoft's SAP FAQ had already encouraged partners to tap into engineering support, marketing materials, and the Azure Cloud Accelerate Factory. It went further, saying you can claim pre-sales assessment funding, the 2.5% deal win bonus, and post-sales deployment funding on the same project. Stacking incentives maximizes your ROI and can cover 20–30% (or more) of the project's first-year Azure value. That's Microsoft's own marketing estimate for FY26, not a measured result. Treat it as an upper bound to test, not a figure to put in a business case.

What CAF doesn't do​

Microsoft presents faster delivery, less repetitive work and more capacity as the program's goals. None of that has been shown for any particular project. CAF doesn't replace partner expertise, and it doesn't remove the customer's responsibility to plan, govern and run its SAP environment.

Section summary: CAF adds free Microsoft engineering to eligible projects. SAP-specialized partners gained access in July 2026, and the benefit can be combined with other incentives.

"AI-Led Growth": The Documented Parts​

"AI-led growth" is marketing language, and this article doesn't treat it as a result. Microsoft's documentation does describe concrete SAP-plus-AI scenarios:

• Using Microsoft Copilot, Copilot Studio and Foundry with SAP systems and data
• Asking questions about SAP information in plain language
• Building agents that reason over SAP data and automate multi-step workflows
• Examples such as checking purchase-order status, procurement approvals, employee leave balances and supply-chain delivery status

Microsoft's Foundry-and-SAP guidance also includes an important caveat. Organizations using SAP APIs and interfaces must comply with SAP's API policy, and Microsoft tells customers to consult SAP or their SAP account team about permitted API use. Connecting an AI agent to an ERP system isn't just a question of which model to use. It raises licensing, permissions and governance questions too.

A documentation warning​

Microsoft's Cloud Adoption Framework has long warned that SAP workloads have complex technical, security and compliance requirements and may not suit a standard migration-factory approach. Its guidance was to build a compatible Azure landing zone, assess the SAP platform and dependent workloads, evaluate sizing, and then migrate.

The article containing that guidance is now marked deprecated. It's no longer updated and is scheduled for removal on October 30, 2026, with readers directed to the SAP on Azure architecture and product documentation instead. That's a change to documentation, not to SAP support policy. Still, save a copy now if your runbooks reference that article.

Section summary: The AI scenarios are real and documented, but they depend on SAP's API policy. One core SAP migration guide is scheduled for removal in late October.

Practical Checklist​

For partners:

1. In Partner Center, check your Infrastructure designation and SAP ACR over the last three months across at least three customers.
2. Pick your skilling route: the AZ-120 certification or the Run SAP on the Microsoft Cloud learning path, which can now be validated in Partner Center.
3. Budget time for the audit.
4. If you're working on ECIF or field-nominated deals, complete the one-time CAF activation.
5. Confirm current FY27 incentive terms before relying on FY26 FAQs.

For customers:

• Ask potential partners whether they hold the SAP on Azure specialization and whether CAF or other funding applies to your project.
• Ask how any AI integration complies with SAP's API policy.
• Keep ownership of governance and operations, whoever does the deployment work.

The Bottom Line​

The September 23 call looks like a routine monthly update, and without a transcript nobody should report it as announcing new requirements, deployments or results. The programs it covers are worth knowing, though. The specialization's requirements have been eased, SAP-specialized partners gained access to CAF in July, and a key SAP migration guide is due to disappear on October 30. For anyone buying or delivering SAP-on-Azure work, those are the practical changes to track.