# Managing identifiers

The **MS365 Identifiers** tool manages the mapping between Peig workspace accounts and Microsoft 365 accounts. It is used during migration to catch discrepancies, and on an ongoing basis to resolve any account mismatches that arise.

## When to use this tool

* A user exists in Microsoft 365 but has no Peig account
* A user exists in Peig but has no Microsoft 365 account
* Accounts exist in both systems but are not linked — typically due to slight differences in email format or identifier
* A user typed their email incorrectly during onboarding and their request needs to be merged with the correct account

## Understanding linked vs. unlinked accounts

An account is **linked** when the identifier in Peig and the identifier in Microsoft 365 have been resolved and aligned. Linked accounts work correctly for device-bound authentication.

An account is **unlinked** when the two systems have records for the same user but the identifiers do not match or have not been associated. Common causes:

* Email address differs slightly between systems
* Accounts were created independently before integration
* A user was added to one system after integration was set up

## Main sections

The MS365 Identifiers tool has two tabs:

**Peig Accounts** — all user accounts in your Peig workspace, their linked status, and their Microsoft 365 identifier if linked.

**Microsoft 365 Accounts** — all user accounts pulled from your Microsoft 365 tenant, their linked status, and their corresponding Peig account if linked.

## Available actions

**Create a Peig account from a Microsoft 365 account**\
Used when a user exists in Microsoft 365 but missed the onboarding window. Open the **Microsoft 365 Accounts** tab, find the user, and click **Create Peig Account**. This creates a placeholder account in Peig pre-linked to the Microsoft 365 account. The user can then complete onboarding normally.

**Create a Microsoft 365 account from a Peig account**\
Used when a user exists in Peig but has no Microsoft 365 account. Open the **Peig Accounts** tab, find the user, and click **Create MS365 Account**.

**Link accounts manually**\
Used when accounts exist in both systems but are not associated. Find the unlinked account in either tab, use the **Link** action, and select the corresponding account in the other system.

**Merge a faulty request**\
If a user mistyped their email during onboarding, their request arrives with the wrong identifier. Rather than asking the user to restart, the Access Admin can merge the request with the correct existing account.

## Tips

{% hint style="info" %}
Run through the MS365 Identifiers tool before closing the migration window — catching discrepancies early prevents sign-in failures after federation is enabled.
{% endhint %}

{% hint style="warning" %}
Identifier mismatches that are not resolved before federation will prevent affected users from signing in. Do not proceed to Step 5 until all accounts are correctly linked.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.peig.io/welcome-to-peig-documentation/deployment-guides/microsoft-365/managing-identifiers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.