What’s happening?
When deploying a custom solution, users encounter an error indicating a missing dependency related to a component in a first-party Microsoft solution.
Reason:
This occurs due to regional deployment policies from Microsoft. Specifically, a dependency or related components from a first-party solution may not be available in the target organization's region at the time of deployment. This typically happens when the source and target organizations are located in different geographical regions (e.g., source in JPN region and target in NAM region), and the latest version of the required solution has not yet been deployed to the target region.
Resolution:
To resolve this, follow these steps:
Wait for the scheduled weekly update from Microsoft, which will deploy the latest version of the required solution (e.g., msdyn_ServiceExtended or msdyn_EmailIntelligence) to the target region. Microsoft typically follows a weekly update and deployment policy, and the solution will become available after the scheduled regional upgrade.
After the regional upgrade has been completed, attempt to deploy your custom solution again. It is recommended to wait at least one hour after the upgrade before retrying the deployment
To see the release schedule for Microsoft Dynamics 365 apps, browse to Released versions of Microsoft Dataverse - Release Notes | Microsoft Learn and select an app from the left navigation.
For example, the release schedule for Customer Service can be found at Released Versions of Dynamics 365 Customer Service - Release Notes | Microsoft Learn.