AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Microsoft Management Agent3/15/2021
Over the years Ive implemented a plethora of solutions to keep licensing consistent with entitlement logic.For some customers this is as simple as everyone gets say, an E3 license.This time to import Office365 licensing information into Microsoft Identity Manager.Im also bringing in the licenses from the tenant as their own ObjectType into the Metaverse.
This includes the information about each license such as how many licenses have been purchased, how many licenses have been issued etc. In the schema I have included the LicensesToAdd and LicensesToRemove attributes. Microsoft Management Agent How To Assign AndCheck out my AddingRemoving User Office365 Licences using PowerShell and the Azure AD Graph RestAPI post to see how to assign and remove licenses using Powershell. From that you can workout your logic to implement an Export flow to manage Office365 licenses. Srens documentation is pretty good but does assume you have a working knowledge of FIMMIM and this blog post is no different. Tip: from a command shell use dir x to get the 8.3 directory format name. Youll need to create a number of corresponding attributes in the Metaverse Schema on the Person ObjectType to flow the attributes into. You will also need to create a new ObjectType in the Metaverse for the O365 Licenses. Use the Schema info below for the attributes that will be imported and the attribute object types to make sure what you create in the Metaverse aligns, so you can import the values.
0 Comments
Read More
Leave a Reply. |