> For the complete documentation index, see [llms.txt](https://bluegamma.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bluegamma.io/documentation/account-and-team-management/security-and-access/login-via-microsoft.md).

# Login via Microsoft

### **1. Overview**

BlueGamma supports authentication via **Microsoft work accounts** using standard OpenID Connect.\
Users log in by selecting **“Sign in with Microsoft”** on the BlueGamma login page.\
All authentication is handled by Microsoft Entra ID; BlueGamma never sees passwords.

***

### **2. Identity Data BlueGamma Receives**

When a user signs in with Microsoft, BlueGamma receives only basic identity fields:

* **Name**
* **Email address**
* **Tenant ID**
* **User ID**

No additional permissions are requested.\
BlueGamma does **not** access mail, calendar, files, or any internal organisational resources.

***

### **3. Restricting Access to Approved Users or Groups**

Your organisation can fully control who is allowed to use BlueGamma by restricting access in **Microsoft Entra ID**.

Below are the standard steps used by IT teams to limit access to a specific user list or security group:

#### **Steps to Restrict Access Using Entra ID**

1. Go to the **Entra Portal**\
   <https://entra.microsoft.com>
2. Navigate to:\
   **Enterprise Applications → BlueGamma**
3. Open **Properties**
4. Set:\
   **User assignment required → Yes**\
   → Only assigned users/groups will be able to sign in.
5. Go to **Users and Groups**
6. Select **Add User / Group**
7. Assign:
   * Individual users, or
   * Security groups (recommended for easier management)
8. Save

Once configured:

* ✔ Assigned users can sign in normally
* ✖ Unassigned users will be blocked from accessing BlueGamma

This is the standard method used by enterprise clients to control platform access.

***

### **4. Optional: Microsoft-Only Authentication**

If your organisation prefers centralised identity management, BlueGamma can disable other login methods and require that **all users authenticate via Microsoft**.

BlueGamma can disable:

* Email & password
* Magic link

This ensures that only users who pass your Microsoft Entra access rules can log in.

To enable this, contact:\
📩 <support@bluegamma.io>

***

### **5. Enterprise SSO (Add-On)**

For organisations requiring deeper integration (e.g., Okta, Ping, OneLogin, enforced IdP login for all users), BlueGamma offers an SSO add-on with optional SCIM provisioning.

This may involve additional cost depending on your plan.

***

### **6. Support**

For assistance with Microsoft login configuration or access control:\
📩 **<support@bluegamma.io>**


---

# 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://bluegamma.io/documentation/account-and-team-management/security-and-access/login-via-microsoft.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.