Lesson Learned #323: Cannot perform creation/scaling of the managed instance due to not enough IPs
We worked on a service request where our customer faced the following error message: Cannot perform creation/scaling of the managed instance as there are not enough available IP addresses in the subnet for performing the operation. For more details visit 'https://aka.ms/determine-subnet-size' and error code: ManagedInstanceIpAddressRangeLimit, scaling their managed instance from General Purpose to Business CriticalLesson Learned #317: Update to service objective for Hub DBs
Today, we worked on a service request where our customer got the following error message scaling database error from General Purpose to Hyperscale "Error message: 'Update to service objective 'xyz' for Hub DBs' is not supported for entity 'DatabaseName'. Following, I would like to share with you our findings.Teams video quality around 1 Mbps in the EMEA region
Since Corona we have noticed very poor video quality (1Mbps). We understand you had a capacity issue and had to set this limit. The limit has been lifted in other regions but not in EMEA. We are paying for this service and use it a lot. We have large meeting rooms based on this and we are getting a lot of negative feedback from our users because if the low video quality. People are now pushing us towards Cisco Webex and we will be installing the first couple of Webex meeting rooms next month. You owe your customers a deadline and some more details about this. And no this is not an issue in our end, we have had support cases with Microsoft and have had this verified.
500 Gateway errors with Teams Chat Bot
Hi, We have a Teams chat bot (aka root bot) that is currently connected to a Skill Dialog bot. When we deploy the root bot and the skill dialog bot to the same app service plan with instance count set to 1, both bots perform per expectations. When we deploy the root bot to its own app service plan with instance count set to 1 and the skill dialog bot with instance count set to 1, both bots perform per expectations. When we deploy the root bot to its own app service plan with instance count set to 2 and the skill dialog bot with instance count set to 2, we start seeing 500 gateway errors. We enabled App Insights and the visualization showed us that communication from the root bot to the skill dialog bot and vice versa would break down and throw the 500 errors. When we deploy the root bot and the skill dialog bot to the same app service plan but have the instance count set to 2, we are also seeing 500 gateway errors. Internally, we suspected that load balancing amongst the instances could be why we are getting the 500 errros. We found a post on Stack Overflow ( https://stackoverflow.com/questions/49651539/how-azure-load-balances-scaled-out-app-service-plan) which seemed to be related to our problem. Since ARR is enabled by default for our web app services, session affinity does not seem to be the issue here. Has anyone come across the same behavior? Any advice? Thank YouEvent resources: Scaling and maintaining your applications on Azure
Hi Folks! Thanks for joining the Reactor Livestream today, it was good fun to go through how to scale and maintain your apps on Azure and how to use the Azure Developer CLI to do that! Resources: Managed Identity Azd Azure OpenAI Chat Repo What is azd? Well Architected Framework - Security Principles Up next: Azure Developer CLI Community Call (24th July @5pm BST) CI/CD for AI (17th July @ 5pm BST) Contact me: LinkedIn GitHub X
