Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Namespace: microsoft.graph
Delete a user's phone authentication method. This removes the phone number from the user and they'll no longer be able to use the number for authentication, whether via SMS or voice calls.
A user can't have an alternateMobile
number without a mobile
number. If you want to remove a mobile
number from a user that also has an alternateMobile
number, first update the mobile
number to the new number, then delete the alternateMobile
number.
If the phone number is the user's default Azure multi-factor authentication (MFA) authentication method, it can't be deleted. Have the user change their default authentication method, and then delete the number.
This API is available in the following national cloud deployments.
Global service | US Government L4 | US Government L5 (DOD) | China operated by 21Vianet |
---|---|---|---|
✅ | ✅ | ✅ | ❌ |
Permissions
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.
Permission type | Least privileged permissions | Higher privileged permissions |
---|---|---|
Delegated (work or school account) | UserAuthenticationMethod.ReadWrite.All | UserAuthenticationMethod.ReadWrite |
Delegated (personal Microsoft account) | Not supported. | Not supported. |
Application | UserAuthenticationMethod.ReadWrite.All | Not available. |
Important
In delegated scenarios with work or school accounts where the signed-in user is acting on another user, they must be assigned a supported Microsoft Entra role or a custom role with a supported role permission. The following least privileged roles are supported for this operation.
- Authentication Administrator
- Privileged Authentication Administrator
HTTP request
Delete your own phone authentication method.
Note
Calling the /me
endpoint requires a signed-in user and therefore a delegated permission. Application permissions aren't supported when using the /me
endpoint.
DELETE /me/authentication/phoneMethods/{phoneMethodId}
Delete your own or another user's phone authentication method.
Note
When calling the /users/{id}
endpoint with {id}
representing the signed-in user, the least privileged delegated permissions are UserAuthenticationMethod.Read for read operations and UserAuthenticationMethod.ReadWrite for write operations.
DELETE /users/{id | userPrincipalName}/authentication/phoneMethods/{phoneMethodId}
The value of phoneMethodId
corresponding to the phoneType to delete is one of the following:
b6332ec1-7057-4abe-9331-3d72feddfe41
to delete thealternateMobile
phoneType.e37fc753-ff3b-4958-9484-eaa9425c82bc
to delete theoffice
phoneType.3179e48a-750b-4051-897c-87b9720928f7
to delete themobile
phoneType.
Request headers
Name | Description |
---|---|
Authorization | Bearer {token}. Required. Learn more about authentication and authorization. |
Request body
Don't supply a request body for this method.
Response
If successful, this method returns a 204 No Content
response code. It doesn't return anything in the response body.
Examples
Request
Here's an example of the request.
DELETE https://graph.microsoft.com/v1.0/me/authentication/phoneMethods/3179e48a-750b-4051-897c-87b9720928f7
Response
Here's an example of the response.
HTTP/1.1 204 No Content