AZ-400 M05L12 Lab Deployment Failures: Outdated Bicep/ARM Templates (Public IP and Storage Account v1)

Open Beginner friendly
#466 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
73/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
azure

Research direction

Start with infra/simple-windows-vm.bicep and follow its linked template to the storage account resource. Check the Public IP allocation setting and the storage account kind against the errors in the issue, then run the lab deployment and Bicep linter. Done means deployment succeeds and the unused-parameter warning is cleared.

Written by the indexing model from the issue text.

Description

Description

The infrastructure deployment step in lab m05l12-ah fails on the hosted Azure DevOps agents due to breaking changes in current Azure resource deployment policies. The template code needs to be updated to match modern Azure requirements.

Defects Found

  1. Standard Public IP SKU Allocation Method Failure

• Error Code: StandardAndStandardV2SkuPublicIPAddressesMustBeStatic
• Error Message: Standard sku publicIp [...] must have AllocationMethod set to Static.
• Root Cause: The template attempts to provision a Standard SKU Public IP address with a Dynamic allocation method. Azure now strictly requires Static allocation for all Standard SKU Public IPs.

  1. Deprecated Storage Account Kind Failure

• Error Code: AccountKindNotSupported
• Error Message: Account Kind Storage is not supported.
• Root Cause: The linkedTemplate deployed by simple-windows-vm.bicep defines a legacy General Purpose v1 storage account (kind: 'Storage'). New creations of this legacy tier are blocked in the lab's deployment region.

  1. Bicep Linter Warning

• Warning: no-unused-params at infra/simple-windows-vm.bicep(20,7)
• Message: Parameter "publicIPAllocationMethod" is declared but never used.

Suggested Fixes

  1. In the Public IP resource definition block, enforce publicIPAllocationMethod: 'Static'.
  2. In the storage account resource definition block (within the nested/linked template), update the kind property from 'Storage' to 'StorageV2'.
  3. Clean up the unused parameter publicIPAllocationMethod from the parameter block of simple-windows-vm.bicep to clear the linter warning.
Dominant language
C#
Stars
248
Forks
4k
PR merge metrics
No merged PRs in 30d

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MicrosoftLearning/eShopOnWeb

All issues in MicrosoftLearning/eShopOnWeb

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.