Open simon-pearson opened 8 months ago
Hi @simon-pearson,
2.33.0 is not the latest Azure CLI(2.54.0).
If you haven't already attempted to do so, please upgrade to the latest Azure CLI version by following https://learn.microsoft.com/en-us/cli/azure/update-azure-cli.
Thank you for opening this issue, we will look into it.
It's worth saying that the same operation fails when you try to do it though the portal, with the same error message (taken from Activity Log):
{
"status": "Failed",
"error": {
"code": "ResourceOperationFailure",
"message": "The resource operation completed with terminal provisioning state 'Failed'.",
"details": [
{
"code": "NameAlreadyExists",
"message": "Call to Microsoft.BotService/botServices failed. Error message: Private link resource already exists",
"details": []
}
]
}
}
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @aznetsuppgithub.
@yonzhan it looks like you're re-assigning this to another team? Can you provide an update?
Describe the bug
I have a private endpoint which targets an Azure Bot Service instance (PE sub-resource type
Bot
). I have created an application security group and am trying to add an association between the application security group and the private endpoint withaz network private-endpoint asg add
. When I run this command I get the following error message:Note that although we get this error message the association does appear to have been added, showing in the Portal:
Related command
az network private-endpoint asg add
Errors
(NameAlreadyExists) Call to Microsoft.BotService/botServices failed. Error message: Private link resource already exists Code: NameAlreadyExists Message: Call to Microsoft.BotService/botServices failed. Error message: Private link resource already exists
Issue script & Debug output
Expected behavior
An association is added between the Bot Service private endpoint and the Application Security Group and the Azure CLI command does not return an error.
Environment Summary
Additional context
No response