Bicep makes Azure resource declarations easier to read, but the file still describes precise infrastructure. Elm Archive uses a parameterized account name and an output referencing the declared resource. The name in the source and the value selected for a deployment are connected through that parameter.
The browser compiler supports primitive literal parameters, objects, arrays, resource declarations and selected earlier local resource references. It does not evaluate arbitrary code or implement the full Bicep language. Modules, loops, decorators and unsupported expressions fail visibly. Use those limits to practice reading a declaration without mistaking the local parser for the official compiler. You will compile a file without deploying it, then apply a supported declaration. The remaining questions distinguish valid local output from proof that a real service or workload is operating.
Compile a supported declaration and keep compilation separate from deployment.