Hey everyone, welcome to another video! Please make sure to read the description for the chapters and key information about this video and others. ⚠ P L E A S E N O T E ⚠ 🤔 Due to the channel growth and number of people wanting help I no longer can answer or even read questions and they will just stay in the moderation queue never to be seen so please post questions to other sites like Reddit, Microsoft Community Hub etc. 🔎 If you are looking for content on a particular topic search the channel. If I have something it will be there! 🕰 I don't discuss future content nor take requests for future content so please don't ask 😇 Thanks for watching! 🤙
Thanks! Great for identity lifecycle straight into Azure AD but very challenging for most of us with identity lifecycle systems running on-prem into AD synchronised/federated to Azure AD
Love this and would have met needs for a project i am running....until the license requirement changed this month to needing a Governance license as well as a P2 license. Microsoft hey!
Well, I'd argue that your Global Admins at least should have the E5 Security Add-on, which includes P2, so they can use PIM - then the governance license purely for those who would administer Lifecycle workflows. No-one likes more cost and I'm completely with the general argument that MSFT do too much to nickle-&-dime their customers, but I think this case might be a rare exception to that rule. Also: if it's only going to be the Global Admins who manage Lifecycle workflows, there's a reduced price for the governance license.
I am currently using Entitlement Management and Identity Governance as a whole "User Management" of one of our business application and pull that out of the applications scope. Super easy to setup and maintain, though not 100% integrated into the app. But better than developing all those features again and again...
I always tell people to go get an M365 Dev tenant to sandbox in. Then you can bring your results forward to your nonprod (if it exists) and then prod tenant.
If someone in the company/org has a Visual Studio Enterprise agreement - which I know isn't everyone's scenario - then that person is also gifted a sandbox tenant plus some E5 licenses under the M365 Developer Program. That said, we created a standalone tenant with a small number of licenses & built it before we built production. It uses SCIM provisioning from our HR systems' pre-production tenant. We're able to use this to test all tenant-level changes before promoting to production, and couldn't imagine doing it any other way without disasters becoming routine.
I'm the Identity & Access guy in my current role - I wonder if Entra will ultimately be the direct replacement for MiM (onPrem, which is included with Azure P2) or competitors like Okta going forward. Thanks for the super-useful overview! 💥
Hey everyone, welcome to another video! Please make sure to read the description for the chapters and key information about this video and others.
⚠ P L E A S E N O T E ⚠
🤔 Due to the channel growth and number of people wanting help I no longer can answer
or even read questions and they will just stay in the moderation queue never to be seen so please post questions to other sites like Reddit, Microsoft Community Hub etc.
🔎 If you are looking for content on a particular topic search the channel. If I have something it will be there!
🕰 I don't discuss future content nor take requests for future content so please don't ask 😇
Thanks for watching!
🤙
First time seeing one of your videos. SUPER!!
Yay! Thank you!
Thanks! Great for identity lifecycle straight into Azure AD but very challenging for most of us with identity lifecycle systems running on-prem into AD synchronised/federated to Azure AD
Love this and would have met needs for a project i am running....until the license requirement changed this month to needing a Governance license as well as a P2 license. Microsoft hey!
im in the same spot...the move to require governance license hurts
Well, I'd argue that your Global Admins at least should have the E5 Security Add-on, which includes P2, so they can use PIM - then the governance license purely for those who would administer Lifecycle workflows.
No-one likes more cost and I'm completely with the general argument that MSFT do too much to nickle-&-dime their customers, but I think this case might be a rare exception to that rule.
Also: if it's only going to be the Global Admins who manage Lifecycle workflows, there's a reduced price for the governance license.
This looks marvelous! I really need to fire up a lab to test these things out! Great presentation
enjoying this video for today learning, thanks a lot!
Perfect timing again. Thank you.
I am currently using Entitlement Management and Identity Governance as a whole "User Management" of one of our business application and pull that out of the applications scope. Super easy to setup and maintain, though not 100% integrated into the app. But better than developing all those features again and again...
Thanks a lot for the video and great explanation.
Great feature! Thanks John
Clear ans presis as always , thank you 👍👍
Always welcome
Great video
Advance happy new year John 🎉
Happy new year!
I always tell people to go get an M365 Dev tenant to sandbox in. Then you can bring your results forward to your nonprod (if it exists) and then prod tenant.
If someone in the company/org has a Visual Studio Enterprise agreement - which I know isn't everyone's scenario - then that person is also gifted a sandbox tenant plus some E5 licenses under the M365 Developer Program.
That said, we created a standalone tenant with a small number of licenses & built it before we built production. It uses SCIM provisioning from our HR systems' pre-production tenant. We're able to use this to test all tenant-level changes before promoting to production, and couldn't imagine doing it any other way without disasters becoming routine.
Thanks sir!
I'm the Identity & Access guy in my current role - I wonder if Entra will ultimately be the direct replacement for MiM (onPrem, which is included with Azure P2) or competitors like Okta going forward.
Thanks for the super-useful overview! 💥
I think it would eventually go in that direction...
Great content as always, greatly appreciated