| 1 | | Hello, the issue is relatively fresh, so I'll give my part. |
| 2 | | |
| 3 | | Windows 10 supports Logins with Microsoft Accounts (Azure Logins, AzureActiveDirectory, ADFS). For such an account no local mapping is created, instead prefix "AzureAD" is used. E.g. "AzureAD\User1". It looks like a domain, but it's a special thingy from Microsoft. |
| 4 | | While AzureAD\User1 is IN the VPN Admin group, the code handling does not deal correctly with Microsoft Accounts I suspect. New patched versions from "validate-user-v2" branch tested. |
| 5 | | |
| 6 | | [[Image(https://i.imgur.com/9tENNdf.png)]] |
| 7 | | |
| 8 | | Many regards |
| 9 | | Max |
| | 1 | Ignore.. it works with AzureAD accounts (v2 branch). |
