Showing results for 
Search instead for 
Did you mean: 

Domain/UPN change causes Priv Access Gateway to not connect

New Contributor



We encounter an issue that when a user's domain / UPN changes from say:

admin@contoso.local > admin@newcontoso.local

The private gateway will fail to establish


In my env Netskope is setup in MultiUser mode(v93.1.0.951) and is integrated with Azure AD for user provisioning / SSO


Reinstalling the Netskope client doesn't resolve the issue


Looking at the device within the Netskope Admin console its client status is 'Multiple Statuses' it will show the same user with both the new domain and the previous domain


Looking at the users profile (updated domain) it will report that the client status is up but physically on the workstation the tunnel will be down and non functional


The only solution that works is to reimage the workstation or assign another device, which feels insane

Has anyone seen this before or have any advice on a resolution?




Community Manager
Community Manager

Hi, @lmunro . Thank you for reaching outA Netskope expert from our community team will get back to you as soon as possible. In the meantime, if any community member knows the solution, please reply to this thread!