Jon Gallant

@yonzhan - Did the redirect port change? I was able to do this before with forwardPorts, but the az cli redirect to localhost port changed recently

Can we configure it to be a static port for the codespace scenario?

Maybe a solution is to add `--redirectPort` to `az login` so we can call expose that port from codespaces devcontainer and then pass that port to `az login`

@jiasli - I'm seeing this again today and don't have a workaround. Can we look into this?

### Issue: `az login` in Codespaces redirects to a random localhost port, causing the redirect to fail. **Analysis and Suggested Changes:** **Option 1: Automatically handle port mapping in Azure CLI**...

@jhendrixMSFT would know best what to do here. I'm open to whatever you decide.

This is how I got the values: ``` output "BING_SEARCH_ENDPOINT" { value = jsondecode(azapi_resource.bing.output).properties.endpoint } output "BING_SEARCH_KEY" { value = jsondecode(data.azapi_resource_action.bing.output).key1 sensitive = true } ``` and add this to...

https://github.com/Azure/aca-landing-zone-accelerator/tree/main/scenarios/aca-internal/bicep This doc starts with azd, but goes into manual deployment making it seem like the user has to do both of those things. Can we rearrange this so there...

This sample should be rearranged so it is easy for a user to either deploy with terraform or with bicep. Right now, there's a hint of using azd with bicep,...

This line should be driven by env vars: https://github.com/Azure/aca-landing-zone-accelerator/blob/main/scenarios/aca-internal/bicep/main.parameters.json#L6