Azure Container Apps
An Azure service that provides a general-purpose, serverless container platform.
325 questions
Container Apps Environment log analytics broken
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(160, 48%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
Brett Styles (AD)
25
Reputation points
PART 1:
When I create a new Log Analytics Workspace from Container Apps Environment it defaults to USA East but my Resources are in Australia East. There is no option to select the region.
- With an existing Container Apps Environment
- Select Log Options
- Select Azure Log Analytics
- Select 'new Log Analytics Workspace'
- Type in a name ws-aue-sensiblename
- Save
This creates the log analytics in East USA, not the same region as my resources, and not compliant with data sovereignty restrictions.
PART 2:
If I then delete the Log Analytics Workspace with a hard delete, the Container Apps Environment logging option is in a permanent indeterminate state with 3 progress bars instead of the usual 3 options. It has been 24 hours now with no change to the state.
How do I clear this locked indeterminate state?
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 93%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBG%3C/text%3E%3C/svg%3E)
Ben Gimblett 3,835 Reputation points Microsoft Employee2023-05-12T08:33:29.9466667+00:00 Hi Brett - thanks for the question
I tried this just now. Using the Azure portal, I created a container app and environment in AU East and the Log Analytics workspace was created in AU East. As a further test I used the UI as described to create a new Log Analytics workspace and this also worked OK. I then tried again in a new resource group in another region and the workspace was still created in AU East. If this persists you may need to contact Azure support to look further. I would definitely recommend to do that for the second issue you described. -
Brett Styles (AD) 25 Reputation points
2023-05-12T09:44:20.8466667+00:00 Thanks, Ben for looking into it. The second issue I managed to fix using PowerShell, so it just seems to be a bug with the UI. I think this all looks pretty new with quite a few minor bugs still present in the UI.
-
Ben Gimblett 3,835 Reputation points Microsoft Employee
2023-05-12T11:18:08.7+00:00 Thanks for the update Brett. Please do raise any suspected UI issues, even minor ones, either through support or even as feedback (via the portal).
Sign in to comment