> For the complete documentation index, see [llms.txt](https://gamelauncher.cloud/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gamelauncher.cloud/help/launchers/microsoft-store/partner-center-setup.md).

# Set Up Your Partner Center Account

Publishing your launcher to the Microsoft Store happens in your own Partner Center account, and before you can submit anything that account has to be associated with a Microsoft Entra ID tenant.

This is a one time setup.

## The three pieces

Every error on this page comes from confusing these.

| Piece                      | What it is                                                                                                                                     |
| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| **Microsoft account**      | The email you personally sign in with, such as `you@outlook.com`. Also called an MSA, or a personal account.                                   |
| **Microsoft Entra tenant** | The directory that holds your company identity, named `yourcompany.onmicrosoft.com`. Accounts that live inside it are work or school accounts. |
| **Partner Center account** | The publisher account that owns the Store listing. It needs a tenant associated to it.                                                         |

**Partner Center accepts work or school accounts** only. A personal Microsoft account can create and administer a tenant perfectly well, but it cannot be used to associate one.

## Step 1: Register on Partner Center

1. Sign up at [partner.microsoft.com](https://partner.microsoft.com).\
   The account is free, and so is publishing your launcher.
2. Start identity verification immediately.\
   Select **Single Developer** or **Company verification**\
   It can take several days and nothing ships until it clears, but everything else on this page can be done while it runs.

## Step 2: Check whether you already have a tenant

When Partner Center tells you `yourcompany.onmicrosoft.com` is not available, do not pick a different name yet.

Those names are globally unique across every Entra tenant in the world, so "not available" very often means **you already created this tenant yourself**, possibly years ago the first time you signed in to Azure, Microsoft 365, or the Store.

## Step 3: Find the tenant you already own

Sign in to [entra.microsoft.com](https://entra.microsoft.com) with the Microsoft account you have used for Microsoft services in the past, then open the directory switcher in the top right.

Each directory's Overview page shows its **Tenant ID** and **Primary domain**. Note both down. Partner Center shows them again on the confirmation screen, and you want to be certain you are associating the right one.

If you find no tenant anywhere, use **Create Microsoft Entra ID** in Step 5 instead. Partner Center builds the tenant and associates it in one go, and you can skip Step 4.

## Step 4: Create a work account with Global Administrator

Check who your administrators are under **Entra ID > Roles & admins > Global Administrator > Assignments**.

If every name listed there is a personal account, an `outlook.com`, `hotmail.com` or `gmail.com` address, you cannot associate the tenant yet. Partner Center rejects those with:

> You can't sign in here with a personal account. Use your work or school account instead.

Create a proper account inside the tenant:

{% stepper %}
{% step %}
Go to **Entra ID > Users > All users** and click **New user > Create new user**.
{% endstep %}

{% step %}
Set the **User principal name** to an address inside your own tenant, such as `admin@yourcompany.onmicrosoft.com`, and give it a display name.
{% endstep %}

{% step %}
Under **Password**, choose auto-generate and copy the password before continuing. It is not shown again.
{% endstep %}

{% step %}
Open the **Assignments** tab, click **Add role**, and pick **Global Administrator**. Then **Review + create**.
{% endstep %}

{% step %}
Sign in once as that account at [login.microsoftonline.com](https://login.microsoftonline.com). Set the permanent password and register multifactor authentication now.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Do not skip that last sign in. The password change and the MFA registration are both forced on first use, and meeting them halfway through the association flow breaks it and sends you back to the start.
{% endhint %}

{% hint style="info" %}
Two details worth knowing:

* **The account must be a member of the tenant.** Users created this way are members by default, but a guest invited in from another directory will not work even with the role.
* **Keep your original personal account as a Global Administrator too.** Two administrators turns a lost password into an inconvenience rather than a support ticket.
  {% endhint %}

## Step 5: Associate the tenant

Open **Account settings > Tenants > Developer** in Partner Center > **Associate Microsoft Entra ID**

Partner Center then signs you out and asks for the Global Administrator of the tenant you are associating, which is not the account you were just using. Sign in with the work account from Step 4.

Do this in a private browsing window. Several Microsoft sessions are usually open by this point, and the account picker will cheerfully reconnect you as the wrong one.

A confirmation screen shows the domain and tenant ID. Check them against what you noted in Step 3, then confirm.

{% hint style="warning" %}
**Every user in the tenant gets Partner Center access automatically, as a default user.** Associate a tenant you control, not a large corporate directory full of people who have no business seeing your Store submissions.
{% endhint %}

## Step 6: Sign in again, then assign roles

When the association succeeds you land on a confirmation page telling you the tenant is connected and that the account you signed in with now holds **Account admin** permissions.

**Sign out and sign back in with your Entra credentials before doing anything else.** The new permissions are carried in your sign in token, so the session you are currently holding does not have them yet. Skipping this makes User management look broken.

Then open **User management** in Partner Center and give each user the role they actually need. Developer and Manager cover most launcher work.

{% hint style="info" %}
Removing a tenant later removes every associated user and their permissions from Partner Center. It leaves the accounts untouched in Entra ID, but the Partner Center side has to be rebuilt by hand.
{% endhint %}

## Next steps

[Publish Store Package (MSIX)](/help/launchers/microsoft-store/msix-package.md)

## Troubleshooting

| What you see                                             | What it means                                                                                                           |
| -------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| "You can't sign in here with a personal account"         | You signed in with an MSA. Do Step 4.                                                                                   |
| "The domain is not available"                            | Usually your own existing tenant, not a squatter. Do Step 2.                                                            |
| "Already associated with another Partner Center account" | A tenant belongs to one Partner Center account at a time. Find the account holding it, or associate a different tenant. |
| A password change or MFA prompt appears mid flow         | The work account was never signed in to. Finish Step 4, then start the association again.                               |
| The tenant is associated, but you cannot assign roles    | Your token predates the association. Sign out and sign back in, as in Step 6.                                           |

***

## Support Assistance

If you need assistance please contact our support \
\- **Dashboard:** <https://app.gamelauncher.cloud/support/overview>\
\- **Discord:** <https://discord.com/invite/FpWvUQ2CJP>

### See our Demo Launcher

[Game Launcher Cloud DEMO - Microsoft Store](https://apps.microsoft.com/detail/9ND7BBBT443B?hl=en-us\&gl=MX\&ocid=pdpshare)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://gamelauncher.cloud/help/launchers/microsoft-store/partner-center-setup.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.