azd deployment

I am getting a few errors when following the azd deployment the best I can from the youtube video here [https://www.youtube.com/watch?v=NagikmsxrHM&t](url)

**- When I run the Initialize-EntraApplication.ps1 I have been getting this error message**

INFO: Configuring logout URL...
WARNING: Failed to configure logout URL: Failed to configure logout URL. Azure CLI returned: ERROR: Bad Request({"error":{"code":"BadRequest","message":"Unable to read JSON request payload. Please ensure Content-Type header is set and payload is of valid JSON format.","innerError":{"date":"2026-05-06T18:34:03","request-id":"df708143-6b79-4010-bb0d-cd11e703c0e9","client-request-id":"df708143-6b79-4010-bb0d-cd11e703c0e9"}}})

- When attempting to deploy using the DevContainers vscode Extension and Docker running in WSL and using key authentication it gives an error when running the Postprovision items.
ERROR: error executing step command 'provision': failed running post hooks: 'postprovision' hook failed with exit code: '1', Path: ''. : exit code: 1, stdout: ========================================
POST-PROVISION: Starting configuration
========================================

[1/4] Granting permissions to CosmosDB...
, stderr: ./bicep/cosmosDb-postDeployPerms.sh: line 1: $'\r': command not found
: invalid option nameDeployPerms.sh: line 3: set: pipefail
✗ ERROR: Failed to grant CosmosDB permissions

I attempted to run azd up, again, however I get the same error. The resources seem to be provisioned, however whatever happens in these post provision steps does not complete.

Start by reproducing azd up in the reported Dev Containers, Docker, WSL, and key-authentication setup, then inspect Initialize-EntraApplication.ps1 and bicep/cosmosDb-postDeployPerms.sh. Done means the logout configuration no longer reports the Azure CLI payload error and the postprovision steps complete successfully without the shell errors.

Written by the indexing model from the issue text.