[BUG] Test failure: Azure.Mcp.Tools.Workbooks.LiveTests.WorkbooksCommandTests.Should_show_workbook_details

[fanyang-mono]

Describe the bug

Link to build: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=5558527&view=logs&j=3062cd78-3dd8-5cfa-d581-ea116ba27da8&t=4af6f21e-660e-510f-93cf-69d2fde1f5df

Error message:

  Failed Azure.Mcp.Tools.Workbooks.LiveTests.WorkbooksCommandTests.Should_show_workbook_details [5 s]
  Error Message:
   Property 'Workbook' not found. Full element: '{"message":"Failed to get workbook: The Resource \u0027Microsoft.Insights/workbooks/39a27c93-d82b-42e4-b22a-a2c0e81577ce\u0027 under resource group \u0027SSS3PT_rg-t2dec7fb2d0864601\u0027 was not found. For more details please go to https://aka.ms/ARMResourceNotFoundFix\nStatus: 404 (Not Found)\nErrorCode: ResourceNotFound\n\nContent:\n{\u0022error\u0022:{\u0022code\u0022:\u0022ResourceNotFound\u0022,\u0022message\u0022:\u0022The Resource \u0027Microsoft.Insights/workbooks/39a27c93-d82b-42e4-b22a-a2c0e81577ce\u0027 under resource group \u0027SSS3PT_rg-t2dec7fb2d0864601\u0027 was not found. For more details please go to https://aka.ms/ARMResourceNotFoundFix\u0022}}\n\nHeaders:\nCache-Control: no-cache\nPragma: no-cache\nx-ms-failure-cause: REDACTED\nx-ms-request-id: f41de918-92d4-4cb1-9223-c393be14714f\nx-ms-correlation-request-id: REDACTED\nx-ms-routing-request-id: REDACTED\nStrict-Transport-Security: REDACTED\nX-Content-Type-Options: REDACTED\nX-Cache: REDACTED\nX-MSEdge-Ref: REDACTED\nDate: Tue, 11 Nov 2025 17:15:31 GMT\nContent-Length: 264\nContent-Type: application/json; charset=utf-8\nExpires: -1\n","stackTrace":"   at Azure.Mcp.Tools.Workbooks.Services.WorkbooksService.GetWorkbook(String workbookId, RetryPolicyOptions retryPolicy, String tenant) in /mnt/vss/_work/1/s/tools/Azure.Mcp.Tools.Workbooks/src/Services/WorkbooksService.cs:line 132\n   at Azure.Mcp.Tools.Workbooks.Commands.Workbooks.ShowWorkbooksCommand.ExecuteAsync(CommandContext context, ParseResult parseResult, CancellationToken cancellationToken) in /mnt/vss/_work/1/s/tools/Azure.Mcp.Tools.Workbooks/src/Commands/Workbooks/ShowWorkbooksCommand.cs:line 65","type":"Exception"}'
  Stack Trace:
     at Azure.Mcp.Tests.TestExtensions.AssertProperty(JsonElement element, String propertyName) in /mnt/vss/_work/1/s/core/Azure.Mcp.Core/tests/Azure.Mcp.Tests/TestExtensions.cs:line 37
   at Azure.Mcp.Tests.TestExtensions.AssertProperty(Nullable`1 element, String propertyName) in /mnt/vss/_work/1/s/core/Azure.Mcp.Core/tests/Azure.Mcp.Tests/TestExtensions.cs:line 33
   at Azure.Mcp.Tools.Workbooks.LiveTests.WorkbooksCommandTests.Should_show_workbook_details() in /mnt/vss/_work/1/s/tools/Azure.Mcp.Tools.Workbooks/tests/Azure.Mcp.Tools.Workbooks.LiveTests/WorkbooksCommandTests.cs:line 84

Expected behavior

Test failed on CI

Actual behavior

Test should pass.

Reproduction Steps

It seems to be flaky.

Environment

No response

[joshfree]

It looks like @matteing added Azure Workbooks support here Azure/azure-mcp@a9acbd3, but there was no matching entry to .github/CODEOWNERS or a GitHub issue label created for it. @KarishmaGhiya can you please work with @matteing and make sure the usual onboarding steps are followed for this partner (http://aka.ms/azmcp/intake) and then lastly help resolve this CI failure?

[joshfree]

It looks like @matteing also isn't a contributor to /microsoft and will need to complete the onboarding steps for their account. /cc @KarishmaGhiya

[KarishmaGhiya]

@fanyang-mono The tests failed because the deployment failed. https://dev.azure.com/azure-sdk/internal/_build/results?buildId=5558527&view=logs&j=30802980-6eba-5be0-4fb7-95f358edc74a&t=8c6bdf1e-51a2-5c7b-53b7-f151659cf507&s=859b8d9a-8fd6-5a5c-6f5e-f84f1990894e If you look for the actual error in the deployment step, it says - Status Message: Database account creation failed. Operation Id: fcee3111-e4b2-4ac0-93de-8f883d66c8d2, Error : Message: {"code":"ServiceUnavailable","message":"Sorry, we are currently experiencing high demand in West US region, and cannot fulfill your request at this time Tue, 11 Nov 2025 16:21:40 GMT. To request region access for your subscription, please follow this link https://aka.ms/cosmosdbquota for more details on how to create a region access request
You'll need to reach out to CosmosDB team to resolve the deployment issue.

[fanyang-mono]

@KarishmaGhiya Can you work with the test owner to get it resolved? I reported this failure, because it failed on one of my previous PR's.