Microsoft is running FY27 Audit Prep Workshops to help partners prepare for specialization audits. The November 19, 2026 announcement highlights process guidance, control-level requirements, and practical advice on documenting the evidence auditors need.
For partners preparing an application or renewal, the immediate value is a chance to resolve uncertainty before an audit becomes a deadline-driven evidence collection exercise. Workshop attendance, however, should support preparation rather than be mistaken for meeting the audit requirements themselves.
What Microsoft announced
Microsoft says selected specializations require periodic audits and that FY27 brought expanded requirements for several security-aligned specializations. The workshops are intended to explain the audit process, review applicable controls, and discuss evidence documentation. Each session includes questions and answers with a Microsoft expert.
The announcement lists the following schedule:
| Date | Workshop topic |
|---|---|
| November 19, 2026 | Infra and Database Migration to Microsoft Azure |
| November 26, 2026 | AI Apps on Microsoft Azure |
| December 3, 2026 | Analytics on Microsoft Azure |
Although the notice discusses security-aligned requirements, the named sessions cover the Azure topics shown above. Partners should verify that a session addresses their specific specialization instead of assuming the schedule covers every security specialization.
Why evidence preparation matters
Audit readiness is more than having a capable delivery team. A partner also needs to demonstrate how its practices satisfy the applicable controls, using evidence that is relevant and understandable to a reviewer.
A practical preparation method is to build a control-to-evidence map. For each current requirement, identify the supporting artifact, its owner, any gaps, and the question it is intended to answer. This is a recommended internal approach, not a new template mandated by the announcement.
That map helps expose a common planning issue: a process may exist, but the team may not have documented it in a form that clearly supports the requirement. Finding such gaps early is more useful than collecting a large folder of loosely related documents immediately before review.
What does—and does not—change by default
The announcement does not state that every partner must undergo an audit. It refers to selected specializations, so the relevant requirements depend on the specialization and its current program rules.
It also does not publish a universal audit deadline, a complete list of revised controls, or a waiver for workshop attendees. Do not infer that joining a session extends a renewal date or guarantees a successful audit.
The appropriate operational response is to confirm your own audit obligations and use the workshop to address specific uncertainties.
Partner next steps
Check the specialization audit workshop registration page for session details and available times. Invite both the person responsible for the specialization and the technical or delivery owners who maintain the supporting evidence.
Before the session, review the current requirements for your specialization and prepare focused questions about unclear controls or evidence expectations. Avoid bringing customer-sensitive material into a general workshop discussion; frame questions around the requirement and evidence type instead.
Afterward, assign owners to any gaps and incorporate the answers into your preparation plan. Keep the applicable program documentation as the reference for mandatory requirements.
Bottom line
These workshops offer a way to reduce uncertainty before a specialization audit. The most useful outcome is not attendance alone, but a clearer evidence plan, named owners, and fewer unanswered questions when the review begins.