PowerPoint Brand Kit Skills Reach Desktop Copilot in October 2026

PowerPoint Brand Kit Skills Put Copilot Instructions in a Markdown File​

The mechanism is simple. According to Microsoft's Message Center notices, brand managers will be able to upload custom presentation skills as Markdown (.md) files to Brand Kit and share them across their organization for use with Copilot in PowerPoint. Microsoft's stated goal is reusable, organization-approved instructions that guide presentation creation.

Microsoft's support page on Brand Skill support confirms that uploaded skills can be a .md file or a .zip file. There is also an option to upload a skill or manually add a skill, so a brand manager can type instructions straight into the Brand Kit without preparing a file. That page sends readers to a separate "Use custom skills with Copilot in PowerPoint" article for skill format guidance. The format rules therefore live outside Brand Kit, and this piece does not try to restate them.

In practice, a skill is a written procedure that Copilot reads before it generates slides. Before this change, Copilot in PowerPoint combined three inputs. Microsoft Support says Copilot primarily uses your sample slides, and secondarily your template's structure and layouts to understand how your organization communicates visually. On top of that, a Brand Kit will apply your brand voice, tone, style and imagery. Skills add a fourth input: the steps an organization wants followed, attached to the same Brand Kit that already holds the visual rules.

Microsoft's Tech Community announcement frames the split this way: Brand Kit helps presentations to start with the appropriate look from your organization, while Skills make familiar workflows repeatable. It is a fair summary. Templates govern layout, and skills govern procedure.

Roadmap 569018 and the Three-Platform Rollout of Brand Skills​

The platform and date records look inconsistent until you notice that Microsoft split this rollout into separate notices for each client. Roadmap 569018 lists Desktop only, with a General Availability ring, the Worldwide (Standard Multi-Tenant) cloud, an October 2026 GA date, and a status of "In development." Microsoft published three Message Center posts covering the same feature:

The web notice is the most specific. Frontier rollout begins mid-September 2026 and is expected to complete by late September 2026, and worldwide General Availability begins in late September 2026 with completion expected by the end of September 2026. The desktop notice only says that rollout begins mid-September 2026. Read alongside the October GA date on roadmap 569018, the likeliest picture is that desktop starts with Frontier in September and reaches general availability in October. No published record states that sequence outright, so treat it as an inference.

Microsoft's own public pages have moved faster than roadmap 569018's status field. The AI at Work roadmap now lists "Now available: Brand Kit and Skills in Copilot in PowerPoint" under generally available features, with an announcement dated September 14. In the Tech Community blog, Microsoft says Brand Kit in PowerPoint and Skills in PowerPoint are generally available today with a Microsoft 365 Copilot license. The roadmap carries its usual warning that all information is subject to change. Admins should treat the "In development" label on the desktop entry as a snapshot rather than a verdict, and should expect tenant-by-tenant availability to follow the staged rollout.

The support documentation reaches wider still. It lists PowerPoint for Microsoft 365, PowerPoint for Microsoft 365 for Mac, PowerPoint for iPhone and PowerPoint for Android phones as applicable clients. For Windows shops, the relevant record is roadmap 569018 and MC1473166: desktop PowerPoint, Worldwide multi-tenant commercial cloud. None of the records mentions government clouds, so the October date and the feature itself should not be assumed for GCC or other sovereign tenants.

How Brand Managers Upload a Skill in the Microsoft Copilot App​

Microsoft Support documents the authoring workflow. It runs in the Microsoft Copilot app rather than in PowerPoint, and it requires ownership or editing rights on a Brand Kit.

1. Open Brand kit from the Microsoft Copilot app.
2. Select a Brand kit that you own or have shared editing access to.
3. Scroll to the bottom, and then select the + icon next to Skills.
4. Choose whether to upload a skill file (.md or .zip) or add one manually.
5. Once you add the skill, confirm that it appears in the Skills section of the Brand kit.

If the skill appears in the Skills section, the upload worked. To change or remove it later, next to each skill, select Edit or Delete as needed. Those two controls are the whole documented lifecycle: there is no version history, approval workflow or staged publishing inside Brand Kit, so any review process has to happen before the upload.

Pay attention to scope. The support page says once added, your brand skill is ready for anyone who has shared access to the Brand kit. Reach is tied to who can see the Brand Kit, not to a separate per-skill audience. Adding a skill to a widely shared kit effectively publishes it to everyone who uses that kit.

Templates reach a Brand Kit through the same app. Microsoft's template guidance has brand owners open the Copilot app, go to Create, then More, then Brand kits, and upload a .potx or .pptx file under Templates. So the brand manager who curates slide masters is usually the same person who will now curate written procedures.

Using a Brand Skill Inside Copilot in PowerPoint​

For end users, a skill is opt-in at the prompt level. Microsoft Support describes the flow:

1. Open PowerPoint, and then open the Copilot pane.
2. In the prompt box, select the + button, and then select Select brand.
3. Choose the Brand kit that contains your skill.
4. With the Brand kit selected, select +, and then select Choose skills.
5. Pick the skill, then enter your prompt as usual.

A skill does not run in the background on every deck. A user has to pick the right Brand Kit and then pick the skill. That gives users control, but adoption depends on people knowing the skill exists. Microsoft's notices list communicating availability as an explicit admin task for exactly this reason.

If a user can't see Copilot at all, the usual licensing and policy checks apply first. Microsoft Support notes that if you don't see Copilot in Word, Excel, PowerPoint, or OneNote, it might not be included with your Microsoft 365 subscription or available based on your organization's settings.

Where Enterprise IT Sees Governance Work in Brand Kit Skills​

The feature does nothing on day one. The Message Center notices state plainly that it is not automatically activated merely because the capability becomes available. A brand manager has to upload and publish a skill first. The affected groups are brand managers who create and publish organizational Brand Kits, and users in organizations where a kit containing a skill has been published and who have access to Copilot in PowerPoint.

The access boundary is already familiar. According to the notices, Brand Kit publishing is governed through the Enterprise Brand Manager policy and a mail-enabled security group, and organizations should confirm that presentation skills use the same controls without additional configuration. Microsoft is telling admins to verify that the existing gate covers the new content type, not promising that it does. Whoever sits in that security group can now publish instructions that shape AI output for everyone using the kit.

Microsoft's recommended actions amount to a small change-management program:

• Review who holds the Brand manager role under the Enterprise Brand Manager policy.
• Name the people who write, review, approve and maintain presentation skills.
• Set up review of skills for security, privacy, accessibility, legal and brand concerns.
• Test skills on representative presentation scenarios before publishing them widely.
• Tell Copilot in PowerPoint users which skills exist and update internal Brand Kit and Copilot documentation.
• Review published skills on a schedule and remove or replace outdated ones.

The compliance section of the notices leaves several questions open. Admins are told to confirm storage, retention, audit logging, Microsoft Purview behavior, user-level disablement, third-party integration and GDPR data-subject-request implications before publishing. Microsoft's current documentation doesn't answer those points. A regulated organization should get those answers before its first skill goes live, not after a skill has spread through hundreds of decks.

The review burden is justified by how skills work. A skill is organization-published text that steers a generative model, and Microsoft's notices describe the change as giving users a new way to interact with generative AI by using organization-published instructions with Copilot in PowerPoint. A stale product claim or an outdated compliance disclaimer in a skill file won't sit unnoticed in a style guide nobody reads. Copilot can repeat it in every deck built with that skill.

Skills Depend on Templates and Sample Slides Already Being Right​

Skills don't fix a weak template. Microsoft's guidance says Copilot draws layouts from the sample slides in a template, and secondarily your template's structure and layouts. If the template has too few sample slides, Copilot falls back to the Slide Master and output quality drops. Microsoft also says templates must be created in PowerPoint for Windows or Mac, not the web, even though they can be used on any platform.

Microsoft's guidance also recommends keeping instructional content out of the template itself, because mixing instructions with regular content may lead to unintended output. Skills give that guidance a proper home. The procedure goes into a Markdown file in Brand Kit, and the template goes back to holding only reusable layouts. Moving any "how to build our quarterly review" slides out of templates and into a skill is a sensible cleanup as the feature arrives. That recommendation is this article's inference from Microsoft's template advice, not a documented migration path.

One gap affects planning. Microsoft's records say what a skill is, but they give no file-size limits, no supported Markdown syntax in Brand Kit itself, and no assurance about how closely Copilot follows a given instruction. Pilot testing is where teams will find out how reliably their instructions are followed.

What this means for you​

Tenant admins should check who holds Brand Manager rights before any skill is published, and should push compliance questions to Microsoft now. End users will see nothing until a brand manager publishes a skill, so there is no emergency. Organizations without Microsoft 365 Copilot licenses aren't affected, because Microsoft ties general availability to that license. Windows desktop users on the Worldwide commercial cloud should expect the feature on roughly the October 2026 timeline in roadmap 569018, while web and Mac users may already have it.

• Audit the members of the mail-enabled security group behind the Enterprise Brand Manager policy, because those people can now publish instructions that steer Copilot for everyone using a shared Brand Kit.
• Confirm with Microsoft or your account team how skills are handled for retention, audit logging, Purview and GDPR requests, since Microsoft's notices list these as open items to check.
• Pilot a skill in a narrowly shared Brand Kit first, because a skill reaches everyone with access to the kit it lives in.
• Treat the "In development" status on roadmap 569018 as out of date, since Microsoft's AI at Work roadmap and Tech Community blog already describe Brand Kit and Skills as generally available.
• Tell users about the + then Choose skills step in the Copilot pane, because skills are applied per prompt and never run automatically.
• Fix templates first by adding representative sample slides, since skills add procedure but Copilot still takes its layouts from the template.

Brand Kit skills are small in technical terms: one Markdown file, a + button and a Choose skills menu. The real change is that written procedures for building presentations become centrally managed content that feeds an AI model, controlled by the same group that already manages logos and templates. Web and Mac tenants are finishing their September rollout, and desktop PowerPoint is due in October. Organizations that settle ownership, review and retention for skills before that desktop release will have their first skills tested and approved when Windows users can start applying them.