[SOLVED] VPN Cisco AnyConnect connecting with wrong email address, how can I change it?

[amateuruser1988]

In Windows 10 I try to connect to host using Cisco AnyConnect Secure Mobility Client.

I get this error:
AADSTS90072: User account '{wrong email address}' from identity provider 'https://sts.windows.net/{some long ID}/' does not exist in tenant 'UiT Office 365' and cannot access the application 'https://vpn.uit.no/saml/sp/metadata/DefaultWEBVPNGroup'(Cisco AnyConnect Studenter) in that tenant. The account needs to be added as an external user in the tenant first. Sign out and sign in again with a different Azure Active Directory user account


The email is not correct, I need to change it. But I can't find any way to change it.

I'm logged into my Azure Active Directory with my correct email address.

I uninstalled and reinstalled Cisco client, but still I get same error.

How can I fix this?

 

[rgd1101]

contact your IT to setup the client?

 

[amateuruser1988]

I just had setup wrong email address in Windows 10 to automatically connect apps to.


On Windows 10:

Settings --> Accounts --> Access work or School --> then choose the wrong email address and click "disconnect".

Then quit VPN Cisco Client. And next time it will ask for new email address and password.

Shame on me, I'm a CS student and the solution was simple.

 

[Ralston18]

Error being:

"AADSTS90072: User account '{wrong email address}' from identity provider 'https://sts.windows.net/{some long ID}/' does not exist in tenant 'UiT Office 365' and cannot access the application 'https://vpn.uit.no/saml/sp/metadata/DefaultWEBVPNGroup'(Cisco AnyConnect Studenter) in that tenant. The account needs to be added as an external user in the tenant first. Sign out and sign in again with a different Azure Active Directory user account '

And the solution being:

"Settings --> Accounts --> Access work or School --> then choose the wrong email address and click "disconnect".

Then quit VPN Cisco Client. And next time it will ask for new email address and password."

Not an intuitive leap from error to solution.

However, after all, you did figure it out.

No shame in that.....