This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(70.4, 31%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ET%3C/text%3E%3C/svg%3E)
Hello
We know that Intune MAM supports two configurations:
Would following variant of #1 is allowed design ??
If I do MDM-enrollment in Intune with primary-user = user1@contoso.com but then accessing intune-sdk app by signing with user2@fabrikam.com which is different AAD-tenant , would this design work ???
Basically I am MAM-enrolling the device into fabrikam.com.
Thanks.
Hi, I was wondering if you were able to find a solution to this problem I'm about to face. One of our departments needs to implement their own Azure Tenant and Intune due to regulations on endpoint devices. Currently, our MDM and MAM policies apply to their devices, both managed and non-managed. But when the migration happens, their devices will be enrolled into their Intune, and our MAM policies will still need to apply to data in our M365. I have come across many articles on integrating third-party MDM solutions, but I haven't found any that address Intune being the third party in this situation. Thank you!
@testuser7 Thanks for posting in our Q&A.
Based on my understanding, this scenario doesn't match Intune MDM + MAM, because intune MDM + MAM means that the device and apps are both managed by a same intune tenant.
Hope it will clarify something.
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
@testuser7 Is there any other assistance that we can provide? If you have any questions or concerns on the recent information I've provided you, please don't hesitate to let me know.
Thanks @Lu Dai-MSFT
Have you practically tested using 2 different Intune tenants i.e., one for MDM enrollment and one for MAM-enrollment ?? Did it fail ?
Unless you have practically tried, your explanation does not look logical.
When MS allows totally 3rd party vendor for MDM-enrollment what's wrong in allowing its own Intune from different tenant ??
@testuser7 An intune tenant can both manage devices and apps. Why you want an intune tenant to manage devices and the other intune tenant to manage apps?
Considering the cost, no one actually does that.
This scenario is MDM for intune tenant 1, or this scenario is unenrolled devices + MAM for intune tenant 2. It is not called intune MDM + MAM.
It is a matter of perception. So instead of debating more on this subjective point, I just want to conclude by practically testing it.
I can not test it because of the right device etc. If you have tested it, let me know so that we can close this thread.