| KB ID: | 4871 |
| Product: | Veeam Data Cloud for Microsoft 365 |
| Published: | 2026-06-16 |
| Last Modified: | 2026-06-16 |
When signing in with a device code during onboarding of a Microsoft 365 organization in Veeam Data Cloud for Microsoft 365, the following error occurs:
AADSTS650051: Consent action for Application '<application-id>' failed due to following error: The <application-id> service principal name is already present for the tenant <tenant-id> paramName: ServicePrincipalName, paramValue: <application-id>, objectType: System.String
This error occurs when a service principal from a previous onboarding attempt is still present in the customer tenant.
Under normal conditions, onboarding proceeds as follows:
However, if an error occurs during organization onboarding (for example, the account does not have sufficient permissions, or an organization with the same domain already exists), onboarding fails after the service principal has been deleted. If a new device code is then generated and used to sign in again too soon, the onboarding process attempts to create a service principal with the same name as the one from the failed attempt. Because service principal deletion is a soft delete that takes approximately 5 to 15 minutes to complete in Azure, the name remains in the tenant even though the Azure portal no longer displays the service principal. As a result, the error occurs.
Deleting the Enterprise application will not speed up removal of the soft-deleted service principal and should not be performed.
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case