<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z0000A8v6OMCQYOkta Classic EngineAdministrationAnswered2026-04-18T09:01:30.000Z2024-05-16T14:49:35.000Z2024-05-31T17:12:06.000Z

0csv7 (0csv7) asked a question.

Office license pulled from user

Over the past few days, we have had Office 365 licenses pulled from a few users and are trying to find out what. Seems to be Okta related.


  • Hello and Thank you for reaching out to the Okta Community! 

     

    The most common cause for this that I've see is the misconfiguration of the groups leveraged for assignments. For example, assigning a group to the O365 app in Okta but not configuring the licenses managed by that group.  

    When you set up Provisioning with Okta, you have to keep in mind that the information flow should be uni-directional, Okta to O365. As such, all role/license management has to be configured only on the Okta side.

    In the cases that I've seen, user provisioning was done from the Okta side, but licenses were assigned/managed from the O365 side which would them be overridden each time an update came down from Okta. 

     

    The Okta Community Questions forum isn't really meant for in-depth troubleshooting. 

    If you already have a Support ticket open, then I recommend continuing the discussion with the assigned Technical Support Engineers. They'll be able to access additional tools and resources to help you get to the bottom of it.  

     

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

     

    --

    Join the discussion for the Ask Me Anything online event on May 23, 2024 with Okta Tactical Edge Product Experts

    Expand Post
    Selected as Best
  • Hello and Thank you for reaching out to the Okta Community! 

     

    The most common cause for this that I've see is the misconfiguration of the groups leveraged for assignments. For example, assigning a group to the O365 app in Okta but not configuring the licenses managed by that group.  

    When you set up Provisioning with Okta, you have to keep in mind that the information flow should be uni-directional, Okta to O365. As such, all role/license management has to be configured only on the Okta side.

    In the cases that I've seen, user provisioning was done from the Okta side, but licenses were assigned/managed from the O365 side which would them be overridden each time an update came down from Okta. 

     

    The Okta Community Questions forum isn't really meant for in-depth troubleshooting. 

    If you already have a Support ticket open, then I recommend continuing the discussion with the assigned Technical Support Engineers. They'll be able to access additional tools and resources to help you get to the bottom of it.  

     

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

     

    --

    Join the discussion for the Ask Me Anything online event on May 23, 2024 with Okta Tactical Edge Product Experts

    Expand Post
    Selected as Best
This question is closed.
Loading
Office license pulled from user