Duplicate subscriptions from overlapping M365/Dynamics 365 integration profiles
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
We've got Microsoft 365 and Dynamics 365/Power Apps SaaS integration profiles both configured against the same tenant. The Dynamics profile isn't scoped to Dynamics-specific licenses — its "Download subscriptions" step pulls the user's entire license set, same as the M365 profile does.
Result: any user with a Dynamics/Power Apps license gets their other Microsoft 365 licenses (Power BI, Copilot, Planner and Project, etc.) duplicated as separate samp_sw_subscription records, one from each profile — both showing up as "Unlicensed subscriptions" in the License Workspace since only one can actually match the owned entitlement. In our case this is ~200 duplicate rows across ~100 users, out of several hundred total flagged as unlicensed.
What we tried: the Subscription Identifier Exclusion Rule, to exclude the overlapping SKUs from the Dynamics profile specifically. It gets rejected — pulled the validating Business Rule and confirmed it only allows excluding an identifier if it's already recognized as belonging to that same profile type's own product definitions. Since something like Power BI Pro is legitimately owned by the M365 integration's product definition, the Dynamics profile can't claim an exclusion for it, even though that's exactly the use case we need.
Has anyone else run into this with overlapping Microsoft integrations on the same tenant? Is there a supported way to scope the Dynamics profile down to Dynamics/Power Apps products only, or any other de-dup mechanism we're missing? Opening a case with ServiceNow as well.
