# IdentityNow and M365

**URL:** <https://community.sailpoint.com/discuss/t/identitynow-and-m365/33603>\
**Category:** Lifecycle & Governance\
**Tags:** connector\
**Created:** [April 21, 2024, 9:23pm UTC](https://community.sailpoint.com/discuss/t/identitynow-and-m365/33603 "2024-04-21T21:23:11Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![adebomol2024](https://avatars.discourse-cdn.com/v4/letter/a/ac91a4/32.png) [@adebomol2024](https://community.sailpoint.com/discuss/u/adebomol2024)\
**Post date:** [April 21, 2024, 9:23pm UTC](https://community.sailpoint.com/discuss/t/identitynow-and-m365/33603/1 "2024-04-21T21:23:11Z")

</div>

I have a question regarding the automation of Microsoft 365 (M365) licenses using SailPoint IdentityNow. Specifically, I’m encountering an issue with the order of assigning Active Directory (AD) groups for licensing.

Does anyone here have experience with using SailPoint IdentityNow to automate M365 licenses for email and Microsoft cloud services? I’m facing a challenge where I’m unsure whether the mailbox needs to be created in the cloud first before assigning the M365 AD group.

Any insights, best practices, or experiences shared would be greatly appreciated!

Thank you in advance for your assistance

---

<div class="post-metadata">

**Author:** ![mfarina](https://sea3.discourse-cdn.com/sailpoint2/discuss/user_avatar/community.sailpoint.com/mfarina/32/16821_2.png) [@mfarina](https://community.sailpoint.com/discuss/u/mfarina)\
**Post date:** [April 22, 2024, 1:23pm UTC](https://community.sailpoint.com/discuss/t/identitynow-and-m365/33603/2 "2024-04-22T13:23:33Z")

</div>

we are going to be moving to M365 next year.

The way we are doing this, is going to be through an all user dynamic group.

membership in the group will prompt M365 to create the mailbox and all related smtp in proxyaddresses as alias’

---

<div class="post-metadata">

**Author:** ![Anass\_AIT\_BEN\_EL\_ARBI](https://avatars.discourse-cdn.com/v4/letter/a/aeb1de/32.png) [@Anass\_AIT\_BEN\_EL\_ARBI](https://community.sailpoint.com/discuss/u/Anass_AIT_BEN_EL_ARBI)\
**Post date:** [April 25, 2024, 11:04am UTC](https://community.sailpoint.com/discuss/t/identitynow-and-m365/33603/3 "2024-04-25T11:04:14Z")

</div>

Hello&nbsp; @adebomol2024 ,

We have achieved something similar result by implementing one of the following approaches:

- Create a dynamic group on your AD that will grant the M365 permissions (plans) and use that group in a role / Access Profile
- Create an Access Profile / Role that contains all the M365 entitlements that are part of the M365 plan, and use that to grant the user access.

You&nbsp;might need to check all the&nbsp;mandatory attributes required to grant the license are provisioned.