![]() However, I cannot disable modern authentication. Inside "Identity", create a new REG_DWORD value called "EnableADAL" and leave the value at 0Īll users work fine. Go to HKEY_CURRENT_USER -> Software -> Microsoft ->Office -> 16.0 ->Common -> Identity Go to the registry editor (Win+R regedit) There currently 180 users within the server farm so re-creating all users UPD isn't an option. Problem has been solved by creating a new user profile disk (UPD) and copying the users data to the newly created UPD. For the non-working registry it get's created with incorrect information or doesn't get created at all. If your web browser auto-fills your username and password, make sure its using your Microsoft 365 email address and password, not your GoDaddy account credentials. Some how the tokenbroker folder is linked to the above working registry on creation and gets created correctly at login. Use your Microsoft 365 email address and password (the same authentication as Workspace Email). If I copy the TokenBroker before logoff and paste it back into the above location I am able to login without been prompted for credentials. Share, store, edit & create files with cloud storage. You may already have an account You can use an email address, Skype ID, or phone number to sign into your Windows PC. Install the Outlook email client on your mobile devices and computers. There is a folder under C:\Users\User\AppData\Local\Packages\_cw5n1h2txyewy\AC\TokenBroker which gets removed by design at logoff. A Microsoft account does not need a Microsoft email The email address used to sign into your Microsoft account can be from, , Gmail, Yahoo, or other providers. This allows you to use your Azure AD credentials to authenticate to the database, instead of using a SQL Server login. HKCU\Software\Microsoft\Office\16.0\Common\Identity\ServiceAuthInfoCache\CredStoreKeyToAuthScheme and a few other places that I’m aware and some that I am not. To efficiently connect from a remote external location to shared data using Microsoft Office to an Azure SQL database, you can use Azure Active Directory authentication. There are specific SID’s that get tied to an account, which I have noticed in a few places within the registry e.g. Even tried recreating a new profile then exporting the working registry keys into a non-working account, you still get prompted for a password at logon to the RDS. I have manually updated the above registry keys, with the correct information. I completely removed the identities registry key HKCU\Software\Microsoft\Office\16.0\Common\Identity, when re-created it uses the information. ![]() Which you can match between the different entries. I’ve done a thorough investigation into this issue and found a few anomalies within the registry.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |