> For the complete documentation index, see [llms.txt](https://docs.cipp.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cipp.app/user-documentation/tenant/administration/partner-relationships.md).

# Partner Relationships

Cross-tenant access policies define how the tenant works with other Microsoft 365 organisations: which external organisations its users can collaborate with through B2B, how much trust is extended to their multi-factor authentication and device compliance claims, and which of them act as a service provider for the tenant. This page lists the organisations that have such a configuration, resolving each one's tenant ID to a readable organisation name.

It is a useful place to spot cross-tenant trust that nobody remembers setting up, including relationships left behind by a previous provider.

## Table Details

| Column                          | Description                                                                                                                                                     |
| ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Tenant                          | The tenant the relationship belongs to. Most useful with All Tenants selected, where rows from every tenant appear together.                                    |
| Tenant Info - Display Name      | The name of the partner organisation, resolved from its tenant ID.                                                                                              |
| Is Service Provider             | Whether the partner is recorded as a service provider for this tenant, which is how a CSP or delegated administration partner appears.                          |
| Is In Multi Tenant Organization | Whether the partner is part of the same multi-tenant organisation as this tenant.                                                                               |
| Tenant Info                     | The full result of the organisation lookup. The cell is a button that opens it in a dialogue, showing the partner's display name, default domain and tenant ID. |

Beyond those, each row is the Graph resource type `crossTenantAccessPolicyConfigurationPartner`, which also carries the inbound and outbound B2B settings, the inbound trust settings and the automatic consent settings for the relationship. For more information on the properties please see the [Graph documentation](https://learn.microsoft.com/en-us/graph/api/resources/crosstenantaccesspolicyconfigurationpartner?view=graph-rest-1.0#properties).

{% hint style="warning" %}
This table is view only. Cross-tenant access settings are changed in the Microsoft Entra admin center.
{% endhint %}

{% hint style="info" %}
The partner name is not stored in the policy itself. CIPP looks up each partner's tenant ID against Microsoft to resolve it, so a partner whose tenant cannot be resolved shows a blank name with its details still available in the Tenant Info column.
{% endhint %}

***

## Feature Requests / Ideas

We value your feedback and ideas. Please raise any [feature requests](https://github.com/CyberDrain/CIPP/issues/new?template=feature.yml) on GitHub.


---

# 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://docs.cipp.app/user-documentation/tenant/administration/partner-relationships.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.