How can we help you today? How can we help you today?
austinjoy

Activity overview

Latest activity by austinjoy

I’m encountering an issue when adding a new Azure SQL Database with a system-managed identity (MI). Here’s the situation: Works on Monitor Server: When I add the Azure SQL Database via the Azure portal from the Monitor server, it works perfectly. Fails from Desktop: However, when I try to add the database from my desktop browser (which is running on an Azure virtual machine), I get the following error: ManagedIdentityCredential authentication unavailable. The requested identity has not been assigned to this resource. Status: 400 (Bad Request) Content: {"error":"invalid_request","error_description":"Identity not found"} (See attached screenshot for full details). It seems like my desktop VM is trying to use its own managed identity rather than the managed identity assigned to the Monitor server. Error Details (from screenshot): Status Code: 400 (Bad Request) Error: "Identity not found" It indicates that the managed identity is either not being recognized or not assigned to the resource (Azure SQL Database). What I’ve Tried So Far: Permission Verification: Both the Monitor server and the desktop VM have the necessary permissions (e.g., Contributor role on the SQL Database and the Resource Group). Cross-Check Managed Identity Settings: I double-checked the managed identity settings on both the Monitor server and desktop VM, ensuring the right identity is assigned. Possible Causes: Identity Confusion Across Different Machines: It seems like the request from my desktop VM is using its own managed identity rather than the Monitor server’s identity. Azure Active Directory Token Assignment: The desktop VM might not have the proper Azure AD token assignment for the SQL Database. Should I be explicitly setting the MI when making the request from the desktop, or is there a configuration in Azure Managed Services that could resolve this conflict? / comments
I’m encountering an issue when adding a new Azure SQL Database with a system-managed identity (MI). Here’s the situation: Works on Monitor Server: When I add the Azure SQL Database via the Azure po...
0 votes
I’m encountering an issue when adding a new Azure SQL Database with a system-managed identity (MI). Here’s the situation: Works on Monitor Server: When I add the Azure SQL Database via the Azure portal from the Monitor server, it works perfectly. Fails from Desktop: However, when I try to add the database from my desktop browser (which is running on an Azure virtual machine), I get the following error: ManagedIdentityCredential authentication unavailable. The requested identity has not been assigned to this resource. Status: 400 (Bad Request) Content: {"error":"invalid_request","error_description":"Identity not found"} (See attached screenshot for full details). It seems like my desktop VM is trying to use its own managed identity rather than the managed identity assigned to the Monitor server. Error Details (from screenshot): Status Code: 400 (Bad Request) Error: "Identity not found" It indicates that the managed identity is either not being recognized or not assigned to the resource (Azure SQL Database). What I’ve Tried So Far: Permission Verification: Both the Monitor server and the desktop VM have the necessary permissions (e.g., Contributor role on the SQL Database and the Resource Group). Cross-Check Managed Identity Settings: I double-checked the managed identity settings on both the Monitor server and desktop VM, ensuring the right identity is assigned. Possible Causes: Identity Confusion Across Different Machines: It seems like the request from my desktop VM is using its own managed identity rather than the Monitor server’s identity. Azure Active Directory Token Assignment: The desktop VM might not have the proper Azure AD token assignment for the SQL Database. Should I be explicitly setting the MI when making the request from the desktop, or is there a configuration in Azure Managed Services that could resolve this conflict? / comments
I’m encountering an issue when adding a new Azure SQL Database with a system-managed identity (MI). Here’s the situation: Works on Monitor Server: When I add the Azure SQL Database via the Azure po...
0 votes
when we talk about It looks like you're encountering issue when adding a new Azure SQL Database with a system-managed identity (MI). Works on Monitor Server: When I add the Azure SQL Database via the Azure portal from the Monitor server, it works perfectly. Fails from Desktop: However, when I try to add the database from my desktop browser (which is running on an Azure virtual machine) ManagedIdentityCredential authentication unavailable. The requested identity has not been assigned to this resource. Status: 400 (Bad Request) Content: {"error":"invalid_request","error_description":"Identity not found"} (See attached screenshot for full details). It seems like my desktop VM is trying to use its own managed identity rather than the managed identity assigned to the Monitor server. Error Details (from screenshot): Status Code: 400 (Bad Request) Error: "Identity not found" It indicates that the managed identity is either not being recognized or not assigned to the resource (Azure SQL Database). What I’ve Tried So Far: Permission Verification: Both the Monitor server and the desktop VM have the necessary permissions (e.g., Contributor role on the SQL Database and the Resource Group). Cross-Check Managed Identity Settings: I double-checked the managed identity settings on both the Monitor server and desktop VM, ensuring the right identity is assigned. Possible Causes: Identity Confusion Across Different Machines: It seems like the request from my desktop VM is using its own managed identity rather than the Monitor server’s identity. Azure Active Directory Token Assignment: The desktop VM might not have the proper Azure AD token assignment for the SQL Database. Should I be explicitly setting the MI when making the request from the desktop, or is there a configuration in Azure Managed Services that could resolve this conflict? / comments
when we talk about It looks like you're encountering issue when adding a new Azure SQL Database with a system-managed identity (MI).Works on Monitor Server: When I add the Azure SQL Database via th...
0 votes
Use Azure Private Link to create a private endpoint for the managed instance, which allows you to access the managed instance over a private network connection. This will help ensure that only authorized users can access the database. Use Azure Virtual Network service endpoints to restrict access to the managed instance to specific subnets within your virtual network. This will help ensure that only resources within those subnets can access the managed instance. Use Azure Active Directory authentication to control access to the managed instance. You can use Azure AD authentication to require users to authenticate with their Azure AD credentials before they can access the database. Use Azure Private Endpoint to create a private endpoint for the managed instance in your virtual network. This will help ensure that only resources within the virtual network can access the managed instance. Use Azure Network Security Groups (NSGs) to restrict access to the managed instance to specific IP addresses or ranges. This will help ensure that only authorized users can access the database. It's important to carefully consider your security needs and choose the approach that best meets your requirements. You may want to use a combination of these approaches to provide the most secure environment for your managed instance. If you are considering migrating your on-premises or other cloud-based systems to Azure, you may want to consider working with an Azure migration consultant. / comments
Use Azure Private Link to create a private endpoint for the managed instance, which allows you to access the managed instance over a private network connection. This will help ensure that only auth...
0 votes