Overview

I developed a scalable content strategy for Agent 365, aligning messaging and experiences to help IT admins confidently manage and secure AI agents across Microsoft 365.

• Skills: Content strategy, content design, AI-assisted workflows, design systems, terminology strategy, cross-functional collaboration

• Audience: Enterprise Microsoft Security customers and internal product teams building Agent 365 security experiences

• Tools: Figma, GitHub Copilot CLI, GitHub, Microsoft 365 suite

• Platforms: Microsoft Entra, Defender, Purview, Security for AI, Microsoft 365 admin center

• Collaborators: 2 product designers, 1 content designer, 50+ cross-functional partners, including content designers, product managers, product marketing managers, and engineers, across Microsoft Security and Microsoft 365 admin center

Problem

As Agent 365 capabilities expanded across Microsoft Security, teams across Entra, Defender, Purview, and Security for AI began communicating Agent 365 value in different ways. Because Agent 365 was owned by the Microsoft 365 admin center team, there was no unified strategy connecting experiences across Microsoft Security products.

At the same time, upcoming licensing changes meant customers using Agent 365 capabilities across Microsoft Security products through our preview program would need to purchase a license to maintain access. Teams needed a consistent approach for communicating Agent 365 value, licensing changes, and customer actions across multiple experiences.

Strategy

Creating a unified Agent 365 content strategy

I collaborated with another content designer on my team to develop a cross-product content strategy to align how teams communicated Agent 365 in Microsoft Security experiences. The framework established:

Messaging principles

• Clearly explain what Agent 365 is and the value it provides

• Focus on actionable customer outcomes instead of abstract product messaging

• Avoid positioning Agent 365 as a native capability of individual security products

Terminology guidance

• Standardized Agent 365 naming conventions

• Defined new AI concepts and terminology

• Established recommended language and terms to avoid

Reusable UX patterns

We partnered with our product designers to define:

• Message patterns by user scenario

• Component guidance

• Content templates

• Do’s and don’ts for Agent 365 messaging

Designing a scalable way to share content guidance

Traditional content strategy guidance was often shared through Figma files or documentation. While effective for designers, these formats were less accessible for PMs, engineers, and other partners who needed to apply the guidance.

To increase adoption, I created an interactive HTML framework that transformed static guidance into a self-service resource. The framework included:

• Decision trees to help teams determine when Agent 365 messaging should appear

• Patterns showing how to structure messages across experiences

• Content guidance with terminology, examples, and anti-patterns

• Cohort frameworks for different customer journeys

I used GitHub Copilot CLI to accelerate development of the framework, allowing me to quickly prototype and deliver a more accessible resource than traditional documentation.

Scaling through AI

The next challenge was extending content strategy beyond what a small content design team could manually support.

We transformed the Agent 365 guidance into an AI-accessible skill stored in our GitHub repository. This allowed teams using GitHub Copilot CLI to access content strategy recommendations directly within their workflows. This created a new model for content design:

Content designers define the strategy. AI helps scale the strategy.

Instead of relying on individual content designers to review every experience, teams could use AI tools to apply established guidance consistently.

Impact

This work established a unified Agent 365 content strategy across Microsoft Security and improved alignment across product organizations.

Outcomes included:

• Created consistent Agent 365 messaging across five Microsoft Security platforms

• Aligned Microsoft Security teams with the Microsoft 365 admin center

• Established shared terminology, value propositions, and content patterns

• Created a scalable framework that made content guidance accessible beyond design teams

• Enabled AI-assisted access to content strategy guidance through GitHub Copilot

This project demonstrated how content design can evolve from creating individual experiences to building systems that help entire organizations create better experiences at scale.