Azure Function Deployment scenarios with 'The remote name could not be resolved' scenarios
I'm trying to debug I'm upgrading from an older version and I've searched everywhere and can't find a clear answer... This might be a silly question, but Quick question that's been bugging me - I'm having trouble deploying my Azure Function App using Azure CLI..... When I run the command `az functionapp create`, it returns an behavior: `The remote name could not be resolved: 'myfunctionapp.azurewebsites.net'`. I've confirmed that my resource group and storage account exist and are correctly configured. Here's the command I'm using: ```bash az functionapp create \ --resource-group myResourceGroup \ --consumption-plan-location westus \ --runtime node \ --runtime-version 14 \ --functions-version 3 \ --name myfunctionapp \ --storage-account mystorageacct ``` I've double-checked the region and the names for any typos. I also tried deploying a simple app with the Azure Portal, but I ran into the same scenario. Additionally, I verified my network settings and ensured that there are no restrictions on outbound calls from my local environment. I can reach the Azure Portal without issues, so it seems to be isolated to the CLI commands. Could there be a DNS resolution scenario in my local environment or with Azure? I've attempted running the command from different networks with no success. Any insights or troubleshooting steps would be greatly appreciated! Is there a better approach? This is part of a larger CLI tool I'm building. What's the best practice here? I'd be grateful for any help. I'm on Ubuntu 20.04 using the latest version of Bash. This is for a REST API running on macOS. Has anyone dealt with something similar?