Status & Stage
Co-Sell Referral Status & Stage Guide
Managing referrals across different cloud marketplaces can be complex because AWS, Azure, and GCP all use different terminology for their statuses and stages.
Suger unifies these into a single, standardized Suger Status to help you track your deals easily without needing to memorize specific definitions for every cloud provider.
This guide explains what each Suger status means and how it maps to the specific status or stage in AWS, Azure, and Google Cloud.
Status Overview & Mappings
The table below shows the correspondence between the unified Suger Status and the native Partner Status/Stage.
| Suger Status | Explanation | AWS Mapping | Azure Mapping | GCP Mapping |
|---|---|---|---|---|
| Draft | The referral is saved as a draft in Suger and has not been submitted to the cloud partner yet. | (Not yet synced) | (Not yet synced) | (Not yet synced) |
| Pending Create | The referral is currently being processed by Suger and will be created on the partner portal shortly. | Pending Create | (N/A) | (N/A) |
| Create Failed | The submission failed. You can hover over the status icon to see the specific error message. | (Error) | (Error) | (Error) |
| Update Failed | A later update to an existing referral failed to reach the cloud partner. The referral still exists — hover over the status icon to see the specific error message. | (Error) | (Error) | (Error) |
| In Review | Successfully submitted. Waiting for the cloud partner to review. | Status: Submitted, In Review | SubStatus: Pending (Outbound) | State: SUBMITTED |
| Pending Acceptance | Action Required: You received an inbound referral. Please accept or decline it to proceed. | Status: Received (Engagement Invitation) | SubStatus: Received (Inbound) | (N/A) |
| Action Required | Action Required: The cloud partner requires updates. Please modify the referral based on feedback and submit again. | Status: Action Required | (N/A) | (N/A) |
| Rejected | The referral was rejected by the cloud partner. | Status: Rejected | SubStatus: Declined | State: NOT_ACCEPTED |
| Expired | The referral expired because it was not approved or rejected within the time limit. | Status: Expired | Status: Expired | (N/A) |
| Active | The referral is active. It has been accepted by the cloud partner or created as a self-led referral. | Status: Approved | Status: Active & SubStatus: Accepted | State: ACCEPTED |
| Closed Won | The referral has been successfully closed as Won. | Stage: Launched | SubStatus: Won | Stage: MIGRATION_IMPL |
| Closed Lost | The referral has been closed as Lost. | Stage: Closed Lost | SubStatus: Lost | Stage: CLOSED_LOST |
| Closed Error | The referral was closed by the cloud partner due to a validation or system error. | (N/A) | SubStatus: Error | Stage: CLOSED_ADMIN |
Azure-only Columns
Two extra columns appear on the Azure tab of the referral list. They are shown by default, and they are removed automatically when you switch to a non-Azure tab — AWS and GCP have no equivalent, so there is nothing to show.
Microsoft Status
Microsoft Status is Microsoft’s own copy of the referral state, shown next to the unified Suger Status. Use it when you need to reconcile against what Partner Center displays rather than what Suger has normalized.
Microsoft expresses the state as a Status plus a Substatus:
| Part | Values |
|---|---|
| Status | New · Active · Closed · None |
| Substatus | None · Pending · Received · Accepted · Won · Lost · Declined · Expired · Error |
The pair is what carries the meaning — for example, Active + Accepted is a referral
Microsoft has taken on, while Closed + Won is a referral Microsoft considers won. The
Suger Status column above collapses these pairs into a single value.
Co-sell Type
Co-sell Type records how the deal is being run with Microsoft:
| Value | Meaning |
|---|---|
| Co-sell | Both you and Microsoft are actively working the deal together. |
| Partner-led | You lead the deal; Microsoft has visibility but is not selling alongside you. |
| Private | The referral is kept private to your organization. |
Understanding Key Features
1. Unified View
Instead of juggling AWS “Stages,” Azure “Sub-statuses,” and GCP “States,” you can rely on the Suger Status column to know exactly where a deal stands in the lifecycle.
Each status carries an in-product tooltip. Hover the status on any referral to read the same explanation the table above gives, without leaving the list.
2. Error Troubleshooting
If a referral enters the Create Failed or Update Failed state:
Hover: You can hover your mouse over the status in the list view to see a card containing the specific error message explaining why it failed.
Detail Page: The error message is also visible directly on the referral detail page.
Cross Cloud Conflict
Not every blocked change shows up as a failure. If you enabled the Prevent duplicate Closed Won validation rule, Suger checks — before moving a referral into the guarded stage — whether the same CRM opportunity has already transacted in a different cloud. When it has, the stage change is skipped rather than rejected: nothing is saved, nothing is pushed to the partner, and no error is returned.
Because that skip is silent, the referral detail page raises a dismissible yellow Cross Cloud Conflict alert instead. It tells you:
- which automatic action was skipped, and the stage it would have moved to;
- which cloud the deal appears to have already transacted in;
- the CRM record value that matched, and a link to the conflicting offer.
What to do: open the linked offer and confirm which cloud the deal genuinely closed in. If this referral should close too, move the stage in the partner portal directly, or turn the validation rule off for that stage mapping. Dismissing the alert only hides it — it does not apply the skipped change.
3. Inbound vs. Outbound Logic
In Review: Generally applies to Outbound referrals (deals you sent to the cloud partner) that are waiting for their approval.
Pending Acceptance: Applies to Inbound referrals (opportunities the cloud partner sent to you) that require your acceptance.
Spotted something wrong or out of date on this page? Tell us and we'll correct it.