Forum Discussion

Dejul Shah's avatar
Dejul Shah
Copper Contributor
Aug 24, 2023

Bing chat enterprise not showing for all users

We have enabled bing chat eneterpise, some users can access Bing chat enterprise, other users who are using edge, and are signed in with their work accounts can not see Bing chat enterpise. I don't understand why some users see and others do not. Is there anything I should be checking on their devices/account

9 Replies

    • Dejul Shah's avatar
      Dejul Shah
      Copper Contributor
      Our issue is resolved, it was a license issue
      E3 users saw bing chat enterprise, E5 users needed to have E3 Extended features licenses added manually to the users to enable bing chat enterprise
      • SimonePS's avatar
        SimonePS
        Copper Contributor
        We had a bunch of users affected and it started to work after deleting Edge cache.
  • aleksey-sobolev's avatar
    aleksey-sobolev
    Copper Contributor
    i have the same issue.
    i have enabled everything and license is properly assigned.
    it was working ok for 1-2 months and suddenly stopped to work.
    i already opened 2 cases and both of them MS support unable to solve it.
    will open a 3rd cases for the same.
  • Dejul Shah - Please open a customer support case. This sounds like it could be an issue of which licenses are assigned to users. Bing Chat Enterprise is available in preview for Microsoft 365 E5, E3, Business Premium and Business Standard licenses. It is also available for faculty at education organizations with Microsoft 365 A3 and A5 licenses.

    Are the users you mentioned on the same or different tenants? It could also be that one tenant is enabled and not another.
    • Dejul Shah's avatar
      Dejul Shah
      Copper Contributor
      I'm not sure how this is related to the question.
      The machine is hybrid joined, and is co-managed by intune.
      • Anonymous's avatar
        Anonymous

        Dejul Shah  

        https://learn.microsoft.com/en-us/mem/intune/configuration/device-restrictions-configure 

        Maybe these limitations are causing the problem?

Resources