# Co-Sell Fields in Microsoft

A reference for the Microsoft solution area and conversation values you map and submit when co-selling through Suger.

---

## Overview

Every Microsoft co-sell referral carries two related values: a **solution area** — the
broad part of the Microsoft portfolio the deal belongs to — and a **conversation**, the
specific motion inside that area. Microsoft validates the pair, so a conversation that
does not belong to the solution area you chose is rejected.

This page lists the current catalog and explains how Suger handles values from earlier
Microsoft fiscal years, which you will still see on older referrals.

To control how these values are pre-filled from your CRM, see
[Field Mapping](/cosell/cosell-configuration/) in the Co-Sell configuration guide. For the
AWS equivalent of this page, see [Co-Sell Fields in ACE](/cosell/cosell-ace-fields/).

## "Solution Play" is now "Conversation"

Microsoft renamed *solution play* to **conversation**. Suger follows the new name, but the
transition leaves a few things worth knowing:

| Where you look | What you see |
| --- | --- |
| **The UI label** | "Solution Play/Conversation" — both names, so the field is findable either way. |
| **The field-mapping key** | Still `SolutionPlay`. Existing mappings keep working; you do not need to rewrite them. |
| **A newly created referral** | Always written as **Conversation**. Suger normalizes on create regardless of which name you sent. |
| **An updated referral** | Whichever name **you** send is preserved. An older client can keep updating `SolutionPlay` without being forced onto the new name. |

## Solution areas and conversations

There are **five** solution areas, carrying **11** area-and-conversation combinations
between them:

| Solution area | Conversation |
| --- | --- |
| **AI Business Solutions** | AI-ready productivity and security for every employee |
| **AI Business Solutions** | Agentify your business processes |
| **AI Business Solutions** | AI in the flow of human ambition |
| **Cloud and AI Platforms** | Modernize with confidence |
| **Cloud and AI Platforms** | Build a unified governed data and AI estate |
| **Cloud and AI Platforms** | Amplify your intelligence |
| **Cloud and AI Platforms** | Ubiquitous Innovation |
| **Microsoft Services** | Accelerate AI Transformation with Microsoft Services |
| **Security** | AI-ready productivity and security for every employee |
| **Security** | Establish a trusted and secure platform for AI |
| **Windows and Devices** | AI Transformation with Surface and Copilot |

Note that **AI-ready productivity and security for every employee** is valid under two
solution areas — **AI Business Solutions** and **Security**. Pick whichever area matches
how the deal is being sold; both pairs are accepted.

:::warning
**`Microsoft Unified` is retired.** It is no longer a selectable solution area. Referrals
created against it in an earlier catalog still exist — see
[Values from earlier catalogs](#values-from-earlier-catalogs) — but you cannot choose it
for anything new.
:::

## Values from earlier catalogs

Microsoft revises this catalog by fiscal year, and Suger handles each generation
differently:

| Situation | What Suger does |
| --- | --- |
| You **create** a referral with a current value | Sent as-is. |
| You **create** a referral with an **FY26** value | Automatically mapped forward to its current equivalent. You do not have to re-pick it. |
| You **update** a referral holding an **FY25** value | **Rejected.** FY25 values were never accepted on update — set a current value on the referral instead. |
| A stored value is outside the current catalog | Displayed with a **`(legacy)`** marker, so you can tell at a glance that the value predates the current catalog. |

The `(legacy)` marker is informational. It does not stop you reading the referral or
working the deal — it tells you that if you edit the referral, you should expect to pick a
current value.

:::tip
If a Microsoft referral fails with a solution-area or conversation error, check the pair
rather than each value alone. A valid area and a valid conversation still fail when the
conversation does not belong to that area — the table above is the authoritative list of
valid combinations.
:::