Forum Discussion

Todd Schultz's avatar
Todd Schultz
Copper Contributor
Oct 17, 2018
Solved

Generic authorization exception inviting Azure AD gests

Recently I have been unable to invite guests to my Azure AD.  This had been working great for over a year but now I get the error "Generic authorization exception" when trying from Powershell or the Azure Portal.  Inviting still works with both methods for those already in the Azure AD (well, the invitee gets the invitation email but not much use since they are already in the Azure AD).

 

  • Hi Todd,

     

    To my understanding "Generic Authorization error" means you don`t have the permission to invite.

    I believe you are the Global Admin.

     

    change the User settings option in the Azure AD Portal.

     

    https://portal.azure.com/#User settings=>External collaboration settings

     

    Admins and users in Guest user role can invite.

     

    toggle this to yes.

     

    https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/directory-assign-admin-roles#guest-inviter

     

     

    Mark like if it helps you. :) 

     

     

     

     

3 Replies

  • M A's avatar
    M A
    Copper Contributor

    Hi Todd,

     

    To my understanding "Generic Authorization error" means you don`t have the permission to invite.

    I believe you are the Global Admin.

     

    change the User settings option in the Azure AD Portal.

     

    https://portal.azure.com/#User settings=>External collaboration settings

     

    Admins and users in Guest user role can invite.

     

    toggle this to yes.

     

    https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/directory-assign-admin-roles#guest-inviter

     

     

    Mark like if it helps you. :) 

     

     

     

     

    • Todd Schultz's avatar
      Todd Schultz
      Copper Contributor
      What you suggested worked so thanks. All I can figure is that Azure must have made a recent change in user invitation authorization because this was working for over a year as it was until maybe last week (i.e., the global administrator didn't need this authorization); I may have missed an Azure change notice or perhaps I mistakenly flipped this switch off somehow.
      • M A's avatar
        M A
        Copper Contributor

        yes, That should be the reason

Resources