> 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/applications/enterprise-apps/spid.md).

# View Enterprise Application

This page shows a single enterprise application in detail: its identifiers and publisher, how exposed the tenant is through it, the credentials it holds, who owns it and who can sign in to it, the permissions and directory roles that have actually been granted to it in the tenant, and the mailbox access Exchange gives it.

The header carries the application's display name, an **Enabled** or **Disabled** chip showing whether the application can sign in and obtain tokens in this tenant, chips for the Application (client) ID and Object ID that copy to the clipboard when selected, how long ago the service principal was created, and a **View in Entra** link that opens the same application in the Microsoft Entra admin center.

## Page Actions

The actions menu offers the same actions as the [Enterprise Applications](https://docs.cipp.app/user-documentation/tenant/administration/applications/enterprise-apps.md#table-actions) table, with the exception of the one that opens this page. All of them act on the application currently in view. **Investigate compromise** opens [NHI Case](https://docs.cipp.app/user-documentation/tenant/administration/nhi/case.md) for this application and starts a new compromise investigation of it.

For an application that uses SAML single sign-on, three further actions manage its token signing certificates. They are greyed out for any other application.

| Action                            | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                |
| --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Add Token Signing Certificate     | Has Entra generate a new token signing certificate for the application, alongside the current one. **Certificate subject** is optional and defaults to `Microsoft Azure Federated SSO Certificate`, with `CN=` added if you leave it off. **Expiry** is optional and defaults to three years, shortened where the tenant's app management policy caps certificate lifetimes. The current certificate keeps signing until you set the new one as preferred. |
| Set Preferred Signing Certificate | Switches the application to sign tokens with the certificate you choose. Greyed out until the application holds more than one signing certificate.                                                                                                                                                                                                                                                                                                         |
| Remove Signing Certificate        | Deletes the signing certificate you choose, together with its private key. The preferred certificate is not offered, so set another as preferred first. Greyed out until the application holds a certificate other than the preferred one.                                                                                                                                                                                                                 |

{% hint style="warning" %}
Switching the preferred certificate takes effect immediately. Any relying party that trusts only the old certificate rejects sign-ins until it is given the new one, so add the new certificate to the relying party before you switch, and remove the old certificate only once nothing trusts it.
{% endhint %}

## View Enterprise App Tab

### Enterprise application

This card identifies the application. The top of the card shows the display name and whether the service principal is enabled or disabled, followed by the details below.

| Field                   | Description                                                                                                                          |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| Display name            | The name of the application as it appears in the tenant.                                                                             |
| Application (client) ID | The application ID, shared by every service principal for this application across all tenants.                                       |
| Object ID               | The object ID of the service principal, unique to this tenant.                                                                       |
| Sign-in audience        | Which account types the application accepts, for example `AzureADMyOrg` for single-tenant or `AzureADMultipleOrgs` for multi-tenant. |
| Publisher               | The publisher name recorded against the application, where one is set.                                                               |
| Homepage                | The application's home page URL, where one is set.                                                                                   |
| Created                 | When the service principal was created in this tenant.                                                                               |

**Open app registration in CIPP** opens [View App Registration](https://docs.cipp.app/user-documentation/tenant/administration/applications/app-registrations/appid.md) for the same application ID.

{% hint style="info" %}
An app registration only exists in the tenant that owns the application. For Microsoft services and third-party multi-tenant applications, the registration lives in the publisher's tenant, so the app registration page will not find it.
{% endhint %}

### Permission exposure

Summarises the application's row from [App Permission Exposure](https://docs.cipp.app/user-documentation/tenant/reports/app-permission-exposure.md): its overall risk, highest impact and suspicion ratings, who owns it, the reasons behind the rating, its sign-in activity and credentials, and each risky permission, directory role and Exchange application role it holds. **Open report** opens the full report for the selected tenant.

Where the application holds nothing from CIPP's risky permissions set, the card says so instead. A note beneath the card says whether the figures come from the report's cached data, and when it was collected, or were read live because the tenant has no cached data yet. Run a sync from the report to refresh cached figures.

The card is not shown with **All Tenants** selected, because the report covers one tenant at a time.

### Single sign-on

Shown only for an application that uses SAML single sign-on. The entry is marked **Configured** when the application has both an identifier and a reply URL, and **Incomplete** otherwise, with the identifier shown beneath the name. Expanding it lists the application's SAML settings alongside the values the relying party needs from Entra.

| Field                            | Description                                                                                          |
| -------------------------------- | ---------------------------------------------------------------------------------------------------- |
| Identifier (Entity ID)           | The identifiers the application is known by in SAML requests.                                        |
| Reply URL (ACS)                  | Where Entra sends the SAML response after sign-in.                                                   |
| Sign-on URL                      | The URL that starts a sign-in from the application's side, where one is set.                         |
| Relay State                      | Where the application sends the user after sign-in completes, where one is set.                      |
| Logout URL                       | Where Entra sends the sign-out response, where one is set.                                           |
| Certificate expiry notifications | The addresses Entra emails before the signing certificate expires.                                   |
| Login / Logout URL (Entra)       | The Entra sign-in and sign-out endpoint to configure in the relying party.                           |
| Entra identifier                 | The issuer the relying party should expect in tokens from Entra.                                     |
| App federation metadata          | A link to the application's federation metadata XML, which many relying parties can import directly. |

### Credentials

Two collapsible entries summarise the credentials held by the service principal, one for client secrets and one for certificates. Each shows how many credentials are configured and the next expiry date, taken from the earliest expiry across all credentials of that type.

For an application that uses SAML single sign-on, a **Token Signing Certificates** entry comes first. It names the certificate currently signing tokens, or is marked in amber when no preferred certificate is set, and shows how many signing certificates the application holds. Expanding it gives the SSO mode, the preferred thumbprint and the next expiry, followed by a table of every signing certificate with its name, thumbprint, whether it is the preferred one, and its start and end dates. Signing certificates are managed with the actions under [#page-actions](#page-actions "mention"), not from this entry.

Expanding an entry lists each credential individually by name and expiry date, along with its key ID. Where the credential list is empty, the entry is marked in amber to draw the eye; that is a prompt to check rather than a fault, since most applications legitimately hold no credentials in the tenants they are consented to.

Each credential carries its own menu:

| Action | Description                                                                                                                                                                                    |
| ------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Rotate | Creates a replacement client secret with the same name and a twelve month lifetime, then deletes the current one. The new secret value is shown once, with a copy button. Client secrets only. |
| Remove | Deletes the selected credential immediately, after a confirmation prompt.                                                                                                                      |

{% hint style="warning" %}
Rotation deletes the original secret as soon as the replacement is created, so anything still using the old value stops working until it is updated. Copy the new secret before closing the dialogue, as it cannot be retrieved afterwards. Where the tenant enforces an application secret lifetime policy, the twelve month lifetime is shortened to fit and you are told so in the result.
{% endhint %}

{% hint style="info" %}
Client secrets and certificate credentials cannot be added from this page, only rotated or removed. A certificate removed here has to be uploaded again in Entra. Token signing certificates are the exception, and can be added with **Add Token Signing Certificate**.
{% endhint %}

### Users and groups

Shows the users and groups assigned to the application and whether assignment is required. With assignment required, only the assigned users and groups can sign in. Without it, everyone in the tenant can. Expanding the entry lists each assignment with the user or group name, whether it is a user or a group, the application role it was given, and when it was assigned. **View User** opens the selected user in CIPP, and is greyed out for groups.

Applications holding permissions on this application are not listed here. Assignments are changed with **Manage Assignments** in the actions menu.

### Owners

Lists the directory objects that own the service principal, with their display name, user principal name, mail address and object type. **View User** opens the selected owner in CIPP, and is offered only for owners that are users rather than groups or other service principals.

Where Graph returns no owners the section says so, and where the owners request fails the error returned by Graph is shown instead. Microsoft first-party service principals routinely have no owners at all.

## Permissions Tab

This tab shows what the application has actually been granted in the tenant, read from the service principal's own app role assignments and OAuth2 permission grants. It reflects consent as it stands now, not what the application asks for in its manifest, so a permission the application requests but has never been consented to will not appear here.

With the `Tenant.Application.ReadWrite` permission, you can also grant and remove permissions here. Each change applies as soon as you confirm it.

| Control                 | Description                                                                                                                                                                                                                                                                                                                                     |
| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Add permission          | Shown beside each section heading. Choose a **Resource API**, then one or more permissions that API publishes. Application permissions are granted with admin consent and take effect without a signed-in user. Delegated permissions are consented on behalf of every user in the tenant. Only APIs CIPP knows the permissions of are offered. |
| Remove (bin icon)       | Shown on each permission. Removes that one permission. Removing a delegated permission also removes any consent individual users gave for it.                                                                                                                                                                                                   |
| Remove all (sweep icon) | Shown on each API group. Removes every permission the application holds on that API, in that section.                                                                                                                                                                                                                                           |

A permission the application already holds is reported as already granted rather than added twice.

### Application permissions

App roles assigned to the application for app-only access, grouped by the API that publishes them. Each group is headed by the resource name, its object ID, and the number of permissions granted. Expanding a group lists each permission by name with the description published by that API.

### Delegated permissions

OAuth2 permission grants where this application is the client, grouped by resource API in the same way. Scopes are de-duplicated and sorted across all grants for that resource, so a scope granted both tenant-wide and to an individual user appears once.

### Risk indicators

Permissions that appear in CIPP's curated set of risky permissions are marked with a coloured bar and a chip reading Critical, High, Medium or Low. Hovering the chip gives the reason the permission is considered risky. Each API group carries a chip of its own showing the highest risk found within it and how many of its permissions are flagged.

{% hint style="info" %}
The risky-permissions set is a deliberately short list of the permissions most useful to an attacker, and it concentrates on application permissions, so delegated scopes are rarely flagged. A permission without a chip has not been assessed rather than judged safe.
{% endhint %}

## Roles Tab

This tab lists the Microsoft Entra directory roles the application holds, whether assigned to it directly or held through membership of a role-assignable group. A role lets the application act as that administrator through any application permission it uses, so a role here can grant far more than the Permissions tab suggests.

Each role shows its name and description, a chip for where it applies (**Directory** for tenant-wide, otherwise the scope it is limited to), and a **Custom** chip for a custom role. A role held through a group carries a **Via group** chip naming the group. Roles in CIPP's risky set carry an **Impact** chip, and hovering it gives the reason the role is considered risky. Where the application holds no roles, the tab says so.

With the `Identity.Role.ReadWrite` permission, you can change the application's roles here. Each change applies as soon as you confirm it.

| Control           | Description                                                                                                                                                                                                                |
| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Add role          | Choose one or more directory roles to assign. Roles are assigned tenant-wide. Roles in CIPP's risky set show their impact in the list, and roles already assigned directly to the application tenant-wide are not offered. |
| Remove (bin icon) | Shown on each directly assigned role. Removes that role from the application, including a role limited to an administrative unit.                                                                                          |
| Remove all        | Removes every directory role assigned directly to the application. Greyed out when it holds none directly.                                                                                                                 |

{% hint style="info" %}
A role held through a group cannot be removed here. Remove the application from the group, or remove the role from the group, to take it away.
{% endhint %}

{% hint style="warning" %}
Privileged roles such as Global Administrator give the application full control of the tenant. CIPP refuses to change the roles of its own CIPP-SAM application.
{% endhint %}

## Exchange Tab

This tab shows the mailbox access Exchange Online gives the application, which is separate from anything granted in Entra. The same access across the whole tenant is listed under [App Mailbox Access](https://docs.cipp.app/user-documentation/email/administration/app-mailbox-access/roles.md).

With the `Tenant.Application.ReadWrite` permission, you can change the application's Exchange access here. CIPP refuses to change the Exchange access of its own CIPP-SAM application.

### Exchange application roles

Lists the Exchange application roles the application holds. These roles do not show as permissions in Entra and add to whatever the application holds there. Each role shows the mailboxes it applies to and a chip for its scope: **Organization**, the management scope or the administrative unit. Roles in CIPP's risky set carry an **Impact** chip, and hovering it gives the suspicion and impact ratings and the reason the role is considered risky. A disabled assignment carries a **Disabled** chip.

Where the application is not registered in Exchange the tab says so, because it cannot hold any roles until it is. Adding a role registers it.

| Control                  | Description                                                                                                                                                                                                                                                                                                            |
| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| New management scope     | Creates a management scope from a **Name** and a **Recipient filter** on mailbox properties, for example `Department -eq 'Sales'`. The scope is created for the whole tenant and can then be used for any role assignment.                                                                                             |
| Remove all               | Removes every Exchange application role the application holds. Greyed out when it holds none.                                                                                                                                                                                                                          |
| Add role                 | Choose one or more **Application roles**, then the **Mailboxes the role applies to**: every mailbox in the organisation, a management scope, or an administrative unit. Roles in CIPP's risky set show their impact in the list. A role the application already holds with the same scope is reported as already held. |
| Change scope (tune icon) | Shown on each role. Assigns the role with the new scope you choose, then removes the current assignment, so the application keeps access throughout.                                                                                                                                                                   |
| Remove (bin icon)        | Shown on each role. Removes that role from the application.                                                                                                                                                                                                                                                            |

Exclusive management scopes do not restrict an application, so they are not offered when choosing a scope.

{% hint style="info" %}
Role changes can take up to two hours to reach an application that is already in use. After a role is removed, the application can keep that mailbox access for up to two hours.
{% endhint %}

### Application access policies

Lists the application access policies that apply to the application. A policy limits which mailboxes the mailbox permissions the application holds in Entra can reach. **RestrictAccess** allows only the members of the named group, and **DenyAccess** every mailbox except theirs. Policies do not limit Exchange application roles. A policy that applies to every application carries an **Every app** chip, and one that Exchange marks invalid, for example because its group was deleted, carries an **Invalid** chip.

Where no policy applies, the application's Entra mailbox permissions reach every mailbox. With the `Tenant.Application.ReadWrite` permission, **Remove policy** (bin icon) removes a policy that names only this application. A policy that applies to every application, or that also names other applications, has to be removed from [Access Policies](https://docs.cipp.app/user-documentation/email/administration/app-mailbox-access/policies.md) instead.

Microsoft is replacing application access policies with Exchange application roles scoped to a management scope or administrative unit, so new policies cannot be created in CIPP.

***

## 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/applications/enterprise-apps/spid.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.
