Allow Tenant-Guests to connect to a Universal Printer of my Company to Print there to
I would like to have the option to add a Guest Account to a specific Printer from my Printer list and let them Print. Maybe we can add another option to only allow Guest Printing from a specific Network, or a possible option to use Guest Printing with Conditional Access Policy, that a Guest can not Print for Fun in our Tenant.AAD Sync
It looks like AAD sync is up and running - it's working with one of my tenants. However, on a second tenant, Edge is telling me that my administration has disabled sync. This is a surprise as I'm the administrator. I can't seem to find a setting for this in AAD - is there one? Or is this just a rollout issue? Thanks!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.
Error creating Azure BOT: Failed to store new BOT
SCENARIO You are trying to create Azure BOT where you are already provided with an existing App registration. After adding relevant details, validation is passed however, the BOT fails to create with Internal Server error. CAUSE This error usually comes up if we are using the same APP ID which is already registered with another Azure BOT resource. { "status": "Failed", "error": { "code": "UnknownError", "message": "Failed to store new bot." } } RESOLUTION Azure BOT requires one to one mapping with the app registration. You can only have one BOT mapped to one App ID. Hence recommendation is to use single app registration for every BOT resource we create.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.Lesson 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.
