About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
missing_linux_example
⚠️
windows_first
⚠️
powershell_heavy
Summary:
The documentation provides command-line examples for Azure CLI (cross-platform) and Azure PowerShell (Windows-centric), but does not include any Linux- or macOS-specific shell examples (e.g., Bash scripting, environment variable handling, or FTP/Git usage from Linux). In the section discussing shell-specific issues (escaping $ in Bash), only a note is provided, without a concrete Bash example. The PowerShell tab is always present, even when it is not supported, and is listed before the portal tab, reinforcing a Windows-first pattern.
Recommendations:
- Add explicit Bash/Linux shell examples for relevant commands, especially where shell escaping or environment differences matter (e.g., using git remote add with $ in the username).
- Include examples of using standard Linux tools (e.g., curl, lftp, git) for FTP/S and Git deployments.
- Where PowerShell is not supported, consider omitting the tab or clearly indicating its absence, and provide parity by including a Bash/Linux tab.
- In tabbed command sections, alternate the order or default to CLI (cross-platform) or Bash before PowerShell to avoid Windows-first perception.
- Add troubleshooting notes or examples for common Linux/macOS issues (e.g., file permissions, SSH key usage, credential storage).
Create pull request
Flagged Code Snippets
# [Azure PowerShell](#tab/powershell)
You can't create user-scope credentials by using Azure PowerShell. Use Azure CLI or the Azure portal to create the credentials, or use app-scope credentials to deploy to FTP/S or local Git.
# [Azure portal](#tab/portal)
In the [Azure portal](https://portal.azure.com), you must have at least one app to use for setting user-scope credentials. The credentials then apply to all apps for all subscriptions in your Azure account that have **SCM Basic Auth** and **FTP Basic Auth** enabled.
1. Select **Deployment Center** under **Deployment** in the left navigation menu of an app.
1. Select the **FTPS credentials** tab, or if **Local Git** is configured as the build source, the **Local Git/FTPS credentials** tab.
1. In the **User-scope** section, add a **Username**.
1. Add and confirm a **Password**.
1. Select **Save**.
-----
After you set user-scope credentials, you can see your deployment user name on your app's **Overview** page in the Azure portal. If local Git deployment is configured, the label is **Git/Deployment username**. Otherwise, the label is **FTP/Deployment username**.

<a name="appscope"></a>
## Get application-scope credentials
The application-scope credentials are automatically created at app creation. The FTP/S app-scope user name always follows the format `app-name\$app-name`. The local Git app-scope user name uses the format `$app-name`.
>[!NOTE]
>When you use `git remote add` in shells that use the dollar sign for variable interpolation, such as Bash, you must use `\$` to escape any dollar signs in the username or password to avoid authentication errors.
You can get your app-scope credentials by using Azure CLI, Azure PowerShell, or the Azure portal.
# [Azure CLI](#tab/cli)
In Azure CLI, get the application-scope credentials by using the [`az webapp deployment list-publishing-profiles`](/cli/azure/webapp/deployment#az-webapp-deployment-list-publishing-profiles) command. For example:
# [Azure PowerShell](#tab/powershell)
In Azure PowerShell, reset the application-scope password by using the [`Invoke-AzResourceAction`](/powershell/module/az.resources/invoke-azresourceaction) command with the `newpassword` action:
The returned Git remote URI doesn't have `/<app-name>.git` at the end. If you use the URI to add a remote, append `/<app-name>.git` to the URI to avoid an error `22` with `git-http-push`.
# [Azure PowerShell](#tab/powershell)
In Azure PowerShell, get the application-scope credentials by using the [`Get-AzWebAppPublishingProfile`](/powershell/module/az.websites/get-azwebapppublishingprofile) command. For example: