Principle 'XYZ' could not be found or this principal type is not supported - Azure SQL DB and MI
In this blog article, we will be discussing the possible scenarios to get the error "Principle 'XYZ' could not be found or this principal type is not supported" while adding an AAD user or group to your Azure SQL database or Azure SQL managed instance.
HTTP ERROR 401 - This page isn’t working right now. However, google Chrome works fine.
Hello all, I am currently getting a HTTP Error 401 message in Edge (Beta). It only happens when trying to authorise via ADFS, Azure AD authorisation is working as expected. When I try the same operation in Google Chrome, everything is working as expected (see pic). I have completed the following: Cleared browser history. Cleared password history. Removed any relevant entries from credential manager Renewed my certificate. Only other relevant info I can think of is that I changed my password at some point last week. Many thanks in advance.
Disable Windows Hello for Business
I am an admin, and attempting to disable "Windows Hello for Business" also referred to as 2-step authentication. From what I gather, this option is set as "disabled" by default. I confirmed this. However Whenever I join a device to Azure AD, it is always prompted with "Windows Hello" and to create a pin. Where can I find the option that allows me to disable this?
Lesson Learned #396: Fixing 'Invalid value for key 'authentication' using System.Data.SqlClient
Our customer is getting the following error message: Application Error System.ArgumentException: Invalid value for key 'authentication'. at System.Data.Common.DbConnectionStringBuilderUtil.ConvertToAuthenticationType(String keyword, Object value) at System.Data.SqlClient.SqlConnectionString.ConvertValueToAuthenticationType() at System.Data.SqlClient.SqlConnectionString..ctor(String connectionString) at System.Data.SqlClient.SqlConnectionFactory.CreateConnectionOptions(String connectionString, DbConnectionOptions previous) at System.Data.ProviderBase.DbConnectionFactory.GetConnectionPoolGroup(DbConnectionPoolKey key, DbConnectionPoolGroupOptions poolOptions, DbConnectionOptions& userConnectionOptions) at System.Data.SqlClient.SqlConnection.ConnectionString_Set(DbConnectionPoolKey key) using in the authentication keyword in the connection string the value Active Directory Managed Identity.
After applying KB5018421 computers cannot be renamed
After applying KB5018421 renaming the computer is no longer possible because the name can't be changed in AAD. Uninstalling the KB allows renaming of the computer. PS C:\windows\system32> Rename-Computer -NewName F57-0 -Restart Rename-Computer : Fail to rename computer 'TEND45D648129B2' to 'F57-0' due to the following exception: Unable to update hostname in Azure AD. Check the event log for detailed error information. At line:1 char:1 + Rename-Computer -NewName F57-0 -Restart + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OperationStopped: (TEND45D648129B2:String) [Rename-Computer], InvalidOperationException + FullyQualifiedErrorId : FailToRenameComputer,Microsoft.PowerShell.Commands.RenameComputerCommandAzure SQL Database Token-based authentication with PowerShell
First published on MSDN on Oct 26, 2018 How to connect to Azure SQL Database using token-based authentication in PowerShell native appsThis guide assumes you already have a deployment of an Azure SQL Database, your PowerShell environment configured and you have an app registration for a native app in Azure Active Directory.
Devices still shows up in AAD after deleting/retiring from Intune
Hi, I have noticed that after deleting/retiring devices (Mobile or Laptop) from Intune, they still show up in Azure Active Directory associated with the user. Is this a know thing? I was expecting them to get devices deleted from AAD once the devices are deleted from Intune. Anyone has encountered this issue or anyone knows what is the best practice to follow? Thanks, YashLesson Learned #380:Unable to load adalsql.dll (Authentication=XYZ).Error code:0x2
Analyzing a support case that our customer got the following error faced: "Unable to load adalsql.dll (Authentication=ActiveDirectoryPassword). Error code: 0x2" using an older application to the Azure SQL database. Following I would like to share my lessons learned about it.
