How do I solve "The registration definition 'eeb6d891-559e-5554-9f5f-b0f6954430c8' not allowed to use the 'dfe4b198-ec21-4e8d-b62f-543cfc923071' as ManagedByTenantId."?

Benjamin Roedell 0 Reputation points
2025-05-19T22:31:10.1066667+00:00

I'm unable to find any reason nor documentation to explain this error message when attempting to onboard a customer

{
	"code": "InvalidTemplateDeployment",
	"details": [
		{
			"code": "InvalidManagedServicesTemplateDeployment",
			"message": "The managed services template deployment file contains invalid values. Please see details.",
			"details": [
				{
					"code": "InvalidRegistrationDefinitionCreateRequest",
					"message": "The registration definition 'eeb6d891-559e-5554-9f5f-b0f6954430c8' not allowed to use the 'dfe4b198-ec21-4e8d-b62f-543cfc923071' as ManagedByTenantId."
				}
			]
		}
	],
	"message": "The template deployment 'Microsoft.Template-20250519165831' is not valid according to the validation procedure. The tracking id is '9a7ef542-73ee-45f4-806a-5fda7ffe8207'. See inner errors for details."
}

This was for a specific resource group and the customer uploading the template has the Owner role for their whole subscription.

Azure Lighthouse
Azure Lighthouse
An Azure service that provides secure managed services and access control for partners and customers.
{count} votes

1 answer

Sort by: Most helpful
  1. Suwarna S Kale 3,951 Reputation points
    2025-05-19T22:54:46.0166667+00:00

    Hello Benjamin Roedell,

    Thank you for posting your question in the Microsoft Q&A forum. 

    The error you're encountering "InvalidRegistrationDefinitionCreateRequest" typically occurs when there's a tenant-level misalignment in Azure's Managed Services onboarding process. Specifically, the error indicates that the ManagedByTenantId (the tenant managing the resources) is not authorized to link with the customer's tenant (the Managed Services registration target). 

    To resolve this, you may verify below configs: 

    • Verify Tenant Permissions: Ensure the customer’s tenant has explicitly granted access to the managing tenant (via Azure Lighthouse) before deployment. 
    • Check Azure AD Trust: Confirm there’s no conditional access policy or cross-tenant restriction blocking the partnership. 
    • Review Template Syntax: Validate that the ManagedByTenantId in the ARM template matches the authorized managing tenant’s ID. 

    If the issue persists, escalate to Microsoft Support with the tracking ID for tenant-level diagnostics. 

    Some reference documentation you may review:

    https://learn.microsoft.com/en-us/azure/lighthouse/how-to/onboard-customer

    If the above answer helped, please do not forget to "Accept Answer" as this may help other community members to refer the info if facing a similar issue. Your contribution to the Microsoft Q&A community is highly appreciated. 


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.