I am trying to assign Entra licenses through ISC roles.
However, I am getting this:
[“50f60901-3181-4b75-8a2c-4c8e4c1d5a72 : 7547a3fe-08ee-4ccb-b430-5077c5041653: License 00000000-0000-0000-0000-000000000000 does not correspond to a valid company License.\t”,“50f60901-3181-4b75-8a2c-4c8e4c1d5a72 : 7547a3fe-08ee-4ccb-b430-5077c5041653: License 00000000-0000-0000-0000-000000000000 does not correspond to a valid company License.\t”]
Have you managed to assign F1, E1 and/or E5 license by adding service entitlements to a role?
Yes in powershell we see all the license packs, take the list and by assigning them to a role in ISC you can manage license. Alternatively you can assign the license to a group and you can assign that group in ISC.
I’ve found that the easiest way to manage licenses is to change the account attribute “assignedLicenses” to an entitlement on the Entra Connector. This will show the SPE_F1, SPE_E3, ect. licenses as entitlements with the ability to associate to a role. Provisioning will work as expected for these.
I have updated “assignedLicenses” to an entitlement on my source; however, after aggregation I still do not see the licenses populated as Entitlement. Is there any other configuration am missing? I also don’t see “assignedLicenses” as an entitlement-aggregation-type during Entitlement aggregation.
By doing it this way, it will come in through the users account aggregation instead of looking for the entitlement during an entitlement aggregation (hence no type).
Try an Account Aggregation and see if they populate. This will use the technical name of the license so look for something along the lines of “SPE_F1” for an F3 license