> For the complete documentation index, see [llms.txt](https://www.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://www.bluegamma.io/documentation/account-and-team-management/security-and-access/login-via-microsoft.md).

# Login via Microsoft

This page provides technical information for IT and Security teams about how Microsoft login works on BlueGamma, what identity data is used, and how your organisation can control access.

### **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.

***

For Microsoft-only login and Enterprise SSO, see [Access Control and SSO](https://www.bluegamma.io/documentation/account-and-team-management/security-and-access/access-control-and-sso.md).

***

### **4. 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.bluegamma.io/documentation/account-and-team-management/security-and-access/login-via-microsoft.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
