| title | application: removeKey |
|---|---|
| description | Remove a key credential from an application |
| ms.localizationpriority | medium |
| author | Jackson-Woods |
| ms.subservice | entra-applications |
| doc_type | apiPageType |
| ms.date | 04/04/2024 |
Namespace: microsoft.graph
Remove a key credential from an application. This method along with addKey can be used by an application to automate rolling its expiring keys.
Note
Create servicePrincipal and Update servicePrincipal operations can continue to be used to add and update key credentials for any application with application or a user's context.
As part of the request validation for this method, a proof of possession of an existing key is verified before the action can be performed.
[!INCLUDE national-cloud-support]
Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions only if your app requires it. For details about delegated and application permissions, see Permission types. To learn more about these permissions, see the permissions reference.
[!INCLUDE permissions-table]
Note
An application does not need any specific permission to roll its own keys.
[!INCLUDE rbac-apps-serviceprincipal-creds-apis]
You can address the application using either its id or appId. id and appId are referred to as the Object ID and Application (Client) ID, respectively, in app registrations in the Microsoft Entra admin center.
POST /applications/{id}/removeKey
POST /applications(appId='{appId}')/removeKey| Name | Description |
|---|---|
| Authorization | Bearer {token}. Required. Learn more about authentication and authorization. |
| Content-Type | application/json. Required. |
In the request body, provide the following required properties.
| Property | Type | Description |
|---|---|---|
| keyId | Guid | The unique identifier for the password. |
| proof | String | A self-signed JWT token used as a proof of possession of the existing keys. This JWT token must be signed with a private key that corresponds to one of the existing valid certificates associated with the application. The token should contain the following claims:
For steps to generate this proof of possession token, see Generating proof of possession tokens for rolling keys. |
If successful, this method returns a 204 No content response code.
The following is example shows how to call this API.
The following example shows a request.
POST https://graph.microsoft.com/v1.0/applications/{id}/removeKey
Content-Type: application/json
{
"keyId": "f0b0b335-1d71-4883-8f98-567911bfdca6",
"proof":"eyJ0eXAiOiJ..."
}[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
The following example shows the response.
HTTP/1.1 204 No Content