text:
Changelog and version.txt for 1.8.2

Changelog and version.txt for 1.8.2

Azure Dev CLI Install Instructions
Install scripts
MacOS/Linux

May elevate using sudo on some platforms and configurations

bash:
curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3813/uninstall-azd.sh | bash;
curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3813/install-azd.sh | bash -s -- --base-url https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3813 --version '' --verbose --skip-verify

pwsh:
Invoke-RestMethod 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3813/uninstall-azd.ps1' -OutFile uninstall-azd.ps1; ./uninstall-azd.ps1
Invoke-RestMethod 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3813/install-azd.ps1' -OutFile install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3813' -Version '' -SkipVerify -Verbose

Windows
PowerShell install
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3813/uninstall-azd.ps1' > uninstall-azd.ps1; ./uninstall-azd.ps1;"
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3813/install-azd.ps1' > install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3813' -Version '' -SkipVerify -Verbose;"

MSI install
powershell -c "irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3813/azd-windows-amd64.msi' -OutFile azd-windows-amd64.msi; msiexec /i azd-windows-amd64.msi /qn"

Standalone Binary

Linux -

x86_64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3813/azd-linux-amd64.tar.gz
ARM64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3813/azd-linux-arm64.tar.gz

MacOS -

x86_64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3813/azd-darwin-amd64.zip
ARM64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3813/azd-darwin-arm64.zip

Windows - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3813/azd-windows-amd64.zip

MSI

https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3813/azd-windows-amd64.msi

Documentation

learn.microsoft.com documentation

title: Azure Developer CLI reference
description: This article explains the syntax and parameters for the various Azure Developer CLI commands.
author: alexwolfmsft
ms.author: alexwolf
ms.date: 04/29/2024
ms.service: azure-dev-cli
ms.topic: conceptual
ms.custom: devx-track-azdevcli
Azure Developer CLI reference
This article explains the syntax and parameters for the various Azure Developer CLI commands.
azd
The Azure Developer CLI (azd) is an open-source tool that helps onboard and manage your application on Azure
Options
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --docs         Opens the documentation for azd in your web browser.
  -h, --help         Gets help for azd.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd auth: Authenticate with Azure.
azd config: Manage azd configurations (ex: default Azure subscription, location).
azd deploy: Deploy the application's code to Azure.
azd down: Delete Azure resources for an application.
azd env: Manage environments.
azd hooks: Develop, test and run hooks for an application. (Beta)
azd init: Initialize a new application.
azd monitor: Monitor a deployed application. (Beta)
azd package: Packages the application's code to be deployed to Azure. (Beta)
azd pipeline: Manage and configure your deployment pipelines. (Beta)
azd provision: Provision the Azure resources for an application.
azd restore: Restores the application's dependencies. (Beta)
azd show: Display information about your app and its resources.
azd template: Find and view template details. (Beta)
azd up: Provision Azure resources, and deploy your project with a single command.
azd version: Print the version number of Azure Developer CLI.

azd auth
Authenticate with Azure.
Options
      --docs   Opens the documentation for azd auth in your web browser.
  -h, --help   Gets help for auth.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd auth login: Log in to Azure.
azd auth logout: Log out of Azure.
Back to top

azd auth login
Log in to Azure.
Synopsis
Log in to Azure.
When run without any arguments, log in interactively using a browser. To log in using a device code, pass
--use-device-code.
To log in as a service principal, pass --client-id and --tenant-id as well as one of: --client-secret,
--client-certificate, or --federated-credential-provider.
azd auth login [flags]

Options
      --check-status                           Checks the log-in status instead of logging in.
      --client-certificate string              The path to the client certificate for the service principal to authenticate with.
      --client-id string                       The client id for the service principal to authenticate with.
      --client-secret string                   The client secret for the service principal to authenticate with. Set to the empty string to read the value from the console.
      --docs                                   Opens the documentation for azd auth login in your web browser.
      --federated-credential-provider string   The provider to use to acquire a federated token to authenticate with.
  -h, --help                                   Gets help for login.
      --redirect-port int                      Choose the port to be used as part of the redirect URI during interactive login.
      --tenant-id string                       The tenant id or domain name to authenticate with.
      --use-device-code[=true]                 When true, log in by using a device code instead of a browser.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd auth: Authenticate with Azure.
Back to top

azd auth logout
Log out of Azure.
Synopsis
Log out of Azure
azd auth logout [flags]

Options
      --docs   Opens the documentation for azd auth logout in your web browser.
  -h, --help   Gets help for logout.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd auth: Authenticate with Azure.
Back to top

azd config
Manage azd configurations (ex: default Azure subscription, location).
Synopsis
Manage the Azure Developer CLI user configuration, which includes your default Azure subscription and location.
Available since azure-dev-cli_0.4.0-beta.1.
The easiest way to configure azd for the first time is to run azd init. The subscription and location you select will be stored in the config.json file located in the config directory. To configure azd anytime afterwards, you'll use azd config set.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
Options
      --docs   Opens the documentation for azd config in your web browser.
  -h, --help   Gets help for config.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config get: Gets a configuration.
azd config list-alpha: Display the list of available features in alpha stage.
azd config reset: Resets configuration to default.
azd config set: Sets a configuration.
azd config show: Show all the configuration values.
azd config unset: Unsets a configuration.
Back to top

azd config get
Gets a configuration.
Synopsis
Gets a configuration in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
azd config get <path> [flags]

Options
      --docs   Opens the documentation for azd config get in your web browser.
  -h, --help   Gets help for get.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage azd configurations (ex: default Azure subscription, location).
Back to top

azd config list-alpha
Display the list of available features in alpha stage.
azd config list-alpha [flags]

Options
      --docs   Opens the documentation for azd config list-alpha in your web browser.
  -h, --help   Gets help for list-alpha.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage azd configurations (ex: default Azure subscription, location).
Back to top

azd config reset
Resets configuration to default.
Synopsis
Resets all configuration in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable to the default.
azd config reset [flags]

Options
      --docs    Opens the documentation for azd config reset in your web browser.
  -f, --force   Force reset without confirmation.
  -h, --help    Gets help for reset.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage azd configurations (ex: default Azure subscription, location).
Back to top

azd config set
Sets a configuration.
Synopsis
Sets a configuration in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
azd config set <path> <value> [flags]

Examples
azd config set defaults.subscription <yourSubscriptionID>
azd config set defaults.location eastus

Options
      --docs   Opens the documentation for azd config set in your web browser.
  -h, --help   Gets help for set.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage azd configurations (ex: default Azure subscription, location).
Back to top

azd config show
Show all the configuration values.
Synopsis
Show all configuration values in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
azd config show [flags]

Options
      --docs   Opens the documentation for azd config show in your web browser.
  -h, --help   Gets help for show.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage azd configurations (ex: default Azure subscription, location).
Back to top

azd config unset
Unsets a configuration.
Synopsis
Removes a configuration in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
azd config unset <path> [flags]

Examples
azd config unset defaults.location

Options
      --docs   Opens the documentation for azd config unset in your web browser.
  -h, --help   Gets help for unset.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage azd configurations (ex: default Azure subscription, location).
Back to top

azd deploy
Deploy the application's code to Azure.
azd deploy <service> [flags]

Options
      --all                   Deploys all services that are listed in azure.yaml
      --docs                  Opens the documentation for azd deploy in your web browser.
  -e, --environment string    The name of the environment to use.
      --from-package string   Deploys the application from an existing package.
  -h, --help                  Gets help for deploy.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd down
Delete Azure resources for an application.
azd down [flags]

Options
      --docs                 Opens the documentation for azd down in your web browser.
  -e, --environment string   The name of the environment to use.
      --force                Does not require confirmation before it deletes resources.
  -h, --help                 Gets help for down.
      --purge                Does not require confirmation before it permanently deletes resources that are soft-deleted by default (for example, key vaults).

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd env
Manage environments.
Options
      --docs   Opens the documentation for azd env in your web browser.
  -h, --help   Gets help for env.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env get-values: Get all environment values.
azd env list: List environments.
azd env new: Create a new environment and set it as the default.
azd env refresh: Refresh environment settings by using information from a previous infrastructure provision.
azd env select: Set the default environment.
azd env set: Manage your environment settings.
Back to top

azd env get-values
Get all environment values.
azd env get-values [flags]

Options
      --docs                 Opens the documentation for azd env get-values in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for get-values.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env list
List environments.
azd env list [flags]

Options
      --docs   Opens the documentation for azd env list in your web browser.
  -h, --help   Gets help for list.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env new
Create a new environment and set it as the default.
azd env new <environment> [flags]

Options
      --docs                  Opens the documentation for azd env new in your web browser.
  -h, --help                  Gets help for new.
  -l, --location string       Azure location for the new environment
      --subscription string   Name or ID of an Azure subscription to use for the new environment

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env refresh
Refresh environment settings by using information from a previous infrastructure provision.
azd env refresh <environment> [flags]

Options
      --docs                 Opens the documentation for azd env refresh in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for refresh.
      --hint string          Hint to help identify the environment to refresh

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env select
Set the default environment.
azd env select <environment> [flags]

Options
      --docs   Opens the documentation for azd env select in your web browser.
  -h, --help   Gets help for select.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env set
Manage your environment settings.
azd env set <key> <value> [flags]

Options
      --docs                 Opens the documentation for azd env set in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for set.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd hooks
Develop, test and run hooks for an application. (Beta)
Options
      --docs   Opens the documentation for azd hooks in your web browser.
  -h, --help   Gets help for hooks.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd hooks run: Runs the specified hook for the project and services
Back to top

azd hooks run
Runs the specified hook for the project and services
azd hooks run <name> [flags]

Options
      --docs                 Opens the documentation for azd hooks run in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for run.
      --platform string      Forces hooks to run for the specified platform.
      --service string       Only runs hooks for the specified service.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd hooks: Develop, test and run hooks for an application. (Beta)
Back to top

azd init
Initialize a new application.
azd init [flags]

Options
  -b, --branch string         The template branch to initialize from. Must be used with a template argument (--template or -t).
      --docs                  Opens the documentation for azd init in your web browser.
  -e, --environment string    The name of the environment to use.
      --from-code             Initializes a new application from your existing code.
  -h, --help                  Gets help for init.
  -l, --location string       Azure location for the new environment
  -s, --subscription string   Name or ID of an Azure subscription to use for the new environment
  -t, --template string       Initializes a new application from a template. You can use Full URI, <owner>/<repository>, or <repository> if it's part of the azure-samples organization.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd monitor
Monitor a deployed application. (Beta)
azd monitor [flags]

Options
      --docs                 Opens the documentation for azd monitor in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for monitor.
      --live                 Open a browser to Application Insights Live Metrics. Live Metrics is currently not supported for Python apps.
      --logs                 Open a browser to Application Insights Logs.
      --overview             Open a browser to Application Insights Overview Dashboard.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd package
Packages the application's code to be deployed to Azure. (Beta)
azd package <service> [flags]

Options
      --all                  Packages all services that are listed in azure.yaml
      --docs                 Opens the documentation for azd package in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for package.
      --output-path string   File or folder path where the generated packages will be saved.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd pipeline
Manage and configure your deployment pipelines. (Beta)
Options
      --docs   Opens the documentation for azd pipeline in your web browser.
  -h, --help   Gets help for pipeline.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd pipeline config: Configure your deployment pipeline to connect securely to Azure. (Beta)
Back to top

azd pipeline config
Configure your deployment pipeline to connect securely to Azure. (Beta)
azd pipeline config [flags]

Options
      --auth-type string             The authentication type used between the pipeline provider and Azure for deployment (Only valid for GitHub provider). Valid values: federated, client-credentials.
      --docs                         Opens the documentation for azd pipeline config in your web browser.
  -e, --environment string           The name of the environment to use.
  -h, --help                         Gets help for config.
      --principal-id string          The client id of the service principal to use to grant access to Azure resources as part of the pipeline.
      --principal-name string        The name of the service principal to use to grant access to Azure resources as part of the pipeline.
      --principal-role stringArray   The roles to assign to the service principal. By default the service principal will be granted the Contributor and User Access Administrator roles. (default [Contributor,User Access Administrator])
      --provider string              The pipeline provider to use (github for Github Actions and azdo for Azure Pipelines).
      --remote-name string           The name of the git remote to configure the pipeline to run on. (default "origin")

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd pipeline: Manage and configure your deployment pipelines. (Beta)
Back to top

azd provision
Provision the Azure resources for an application.
azd provision [flags]

Options
      --docs                 Opens the documentation for azd provision in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for provision.
      --no-state             Do not use latest Deployment State (bicep only).
      --preview              Preview changes to Azure resources.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd restore
Restores the application's dependencies. (Beta)
azd restore <service> [flags]

Options
      --all                  Restores all services that are listed in azure.yaml
      --docs                 Opens the documentation for azd restore in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for restore.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd show
Display information about your app and its resources.
azd show [flags]

Options
      --docs                 Opens the documentation for azd show in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for show.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd template
Find and view template details. (Beta)
Options
      --docs   Opens the documentation for azd template in your web browser.
  -h, --help   Gets help for template.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd template list: Show list of sample azd templates. (Beta)
azd template show: Show details for a given template. (Beta)
azd template source: View and manage template sources. (Beta)
Back to top

azd template list
Show list of sample azd templates. (Beta)
azd template list [flags]

Options
      --docs            Opens the documentation for azd template list in your web browser.
  -h, --help            Gets help for list.
  -s, --source string   Filters templates by source.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd template: Find and view template details. (Beta)
Back to top

azd template show
Show details for a given template. (Beta)
azd template show <template> [flags]

Options
      --docs   Opens the documentation for azd template show in your web browser.
  -h, --help   Gets help for show.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd template: Find and view template details. (Beta)
Back to top

azd template source
View and manage template sources. (Beta)
Options
      --docs   Opens the documentation for azd template source in your web browser.
  -h, --help   Gets help for source.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd template: Find and view template details. (Beta)
azd template source add: Adds an azd template source at the specified key (Beta)
azd template source list: Lists the configured azd template sources. (Beta)
azd template source remove: Removes the specified azd template source (Beta)
Back to top

azd template source add
Adds an azd template source at the specified key (Beta)
azd template source add <key> [flags]

Options
      --docs              Opens the documentation for azd template source add in your web browser.
  -h, --help              Gets help for add.
  -l, --location string   Location of the template source.
  -n, --name string       Display name of the template source.
  -t, --type string       Kind of the template source.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd template source: View and manage template sources. (Beta)
Back to top

azd template source list
Lists the configured azd template sources. (Beta)
azd template source list [flags]

Options
      --docs   Opens the documentation for azd template source list in your web browser.
  -h, --help   Gets help for list.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd template source: View and manage template sources. (Beta)
Back to top

azd template source remove
Removes the specified azd template source (Beta)
azd template source remove <key> [flags]

Options
      --docs   Opens the documentation for azd template source remove in your web browser.
  -h, --help   Gets help for remove.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd template source: View and manage template sources. (Beta)
Back to top

azd up
Provision Azure resources, and deploy your project with a single command.
azd up [flags]

Options
      --docs                 Opens the documentation for azd up in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for up.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd version
Print the version number of Azure Developer CLI.
azd version [flags]

Options
      --docs   Opens the documentation for azd version in your web browser.
  -h, --help   Gets help for version.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

authors: azure-sdk weikanglim

repo: Azure/azure-dev


text:
Importing a VM throws a BlobDoesNotExistInStorageAccount error

I have a VM I am trying to import from one lab into another. Labs belong to different subscriptions, owned by the same tenant. This is the error I am getting after 1 h of the script going on:
Invoke-AzResourceAction: BlobDoesNotExistInStorageAccount : The blob name:  was not found in the lab storage account: , container: datadisks
Write-Error: Failed to migrate VM '' from Lab '' to Lab ''.

@flixman, which script are you running? Can you elaborate? From the error message it appears like the VM and Lab names are not provided or determined at runtime.

@leovms Sorry, my bad: the script I am referring to is ImportVirtualMachines_ps6.ps1. I have checked that I have contributor permissions on the destination Storage account.

@leovms Is there anything else I can help with? I need to import a number of machines, and this issue is really blocking me :s Is there any workaround I can use while this is being investigated?

@flixman, I would need to repro your issue. Can you provide sample parameters you are passing? It is not necessary that you give concrete values for subscription ID, for example. I just need the pseudos of the values you pass. Also, does the image you are trying to import have data disks?

We discovered this to be a product bug. The fix has since been deployed. Sorry for the inconvenience.

source: gharchive/issue

authors: flixman joerage leovms

repo: Azure/azure-devtestlab

license: mit

license_type: permissive

license_source: bigquery


text:
Connecting to EXO with modern auth

Hi
I'm trying to connect to EXO using modern auth without dependency on the available module.
`Add-Type -Path "C:\Program Files\WindowsPowerShell\Modules\AzureAD\2.0.2.16\Microsoft.IdentityModel.Clients.ActiveDirectory.dll"
Add-Type -Path "C:\Program Files\WindowsPowerShell\Modules\AzureAD\2.0.2.16\Microsoft.IdentityModel.Clients.ActiveDirectory.Platform.dll"
$clientID = "a0c73c16-a7e3-4564-9a95-2bdf47383716"
$redirectURI = "urn:ietf:wg:oauth:2.0:oob"
$resourceID = "https://outlook.office365.com/PowerShell-LiveId"
$platformParameters = New-Object "Microsoft.IdentityModel.Clients.ActiveDirectory.PlatformParameters" -ArgumentList "Auto"
$userCredential = New-Object "Microsoft.IdentityModel.Clients.ActiveDirectory.UserCredential" -ArgumentList ""
$authContext = New-Object Microsoft.IdentityModel.Clients.ActiveDirectory.AuthenticationContext -ArgumentList "https://login.windows.net//"
$authResult = $authContext.AcquireTokenAsync($resourceID, $clientID, [Uri]$redirectURI, $platformParameters, $userCredential).Result `
On both ADAL 3.18 and 3.19 I'm getting the infamous "Cannot find overload..." error. Can anyone point me in the right direction for doing this? I hope it's possible to get the same kind of connection as by using the module this way (including refresh token).
Thanks!

Yeah they changed that, as they are wont to do.  I think there are a couple of problems with your code.  The argument for authenticationcontext should have the path of "common" (at least, I couldn't get it to work with what I had).  And the resourceId can't have the path, because the authorization is for the root.  This is what I did to make it work (along with connecting the session):
(Import-Module -Name AzureAD -PassThru) |
ForEach-Object {
Add-Type -Path "$($.ModuleBase)\Microsoft.IdentityModel.Clients.ActiveDirectory.dll"
Add-Type -Path "$($.ModuleBase)\Microsoft.IdentityModel.Clients.ActiveDirectory.Platform.dll"
}
$resourceID = "https://outlook.office365.com"
$client_id = "a0c73c16-a7e3-4564-9a95-2bdf47383716" # Exchange Online Powershell ID
$redirectURI = "urn:ietf:wg:oauth:2.0:oob" # Redirect URI for Exchange Online
$authContext = [Microsoft.IdentityModel.Clients.ActiveDirectory.AuthenticationContext]::new("https://login.windows.net/common/")
$AADcredential = [Microsoft.IdentityModel.Clients.ActiveDirectory.UserCredential]::new()
$platformParameters = [Microsoft.IdentityModel.Clients.ActiveDirectory.PlatformParameters]::new([Microsoft.IdentityModel.Clients.ActiveDirectory.PromptBehavior]::Auto)
$UserID =  [Microsoft.IdentityModel.Clients.ActiveDirectory.UserIdentifier]::AnyUser
$authContext.AcquireTokenAsync($resourceID,$client_id,$redirectURI,$platformParameters,$UserID)
If  (-not $authReply.IsFaulted) {
$token = $authReply.Result
$EncodedBasicCredential = [System.Management.Automation.PSCredential]::new($authReply.Result.UserInfo.DisplayableId,(ConvertTo-SecureString -AsPlainText -Force -String ($authReply.Result.AccessTokenType + " " + $authReply.Result.AccessToken)))
$session = New-PSSession -Name ExchangeOnline -ConnectionUri "$resourceID/PowerShell-LiveId?BasicAuthToOAuthConversion=true" -ConfigurationName Microsoft.Exchange -Credential $EncodedBasicCredential -Authentication Basic
$session
}

Hi @glennvanrymenant
Thank you for your issue submission. Unfortunately, this appears to be a problem with the cmdlt and a support issue. Issues in this repo are for documentation issues. You can try one of the following links for additional help.
Microsoft Support: https://support.microsoft.com/
Azure AD forums: https://social.technet.microsoft.com/Forums/en-US/home?forum=windowsazureaditpro
Stackoverflow: https://stackoverflow.com/

authors: billmath glennvanrymenant jordanmills

repo: Azure/azure-docs-powershell-azuread

license_source: github-api


text:
Docs.MS CI Updates for Azure.Security.KeyVault.Administration

CI Update for release of Azure.Security.KeyVault.Administration

Docs Build status updates of commit 5a96ac0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

bundlepackages/azure-dotnet-preview.csv
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

source: gharchive/pull-request

authors: VSC-Service-Account azure-sdk

repo: Azure/azure-docs-sdk-dotnet


text:
Docs.MS Release Updates for azure-resourcemanager-sql

Update docs metadata and targeting for release of azure-resourcemanager-sql

Docs Build status updates of commit 4f836b5:
:clock10: Full build: the average full build time is 82 min(s) 3 sec(s), this is based on the last 661 build(s) for this repository.

Docs Build status updates of commit 4f836b5:
:clock10: Full build: the average full build time is 82 min(s) 4 sec(s), this is based on the last 662 build(s) for this repository.

repo: Azure/azure-docs-sdk-java


text:
Fix unit tests when ran locally

Quick fix for tests that were failing locally due to not accounting for daylight savings differences on local machine.

@microsoft-github-policy-service agree

@microsoft-github-policy-service rerun

repo: Azure/azure-functions-dotnet-worker

license: MIT


text:
Fix issue 718

Fix issue #718

please submit this against dev branch

authors: marianosz soninaren

repo: Azure/azure-mobile-services


text:
[Microsoft Azure Data Manager for Agriculture - Microsoft Azure Data Manager for Agriculture] API Review

New API Review meeting has been requested.
Service Name: Microsoft Azure Data Manager for Agriculture - Microsoft Azure Data Manager for Agriculture
Review Created By: Abhishek Khatri
Review Date: 05/08/2024 09:00 AM PT
Release Plan:
PR: https://github.com/Azure/azure-rest-api-specs/pull/28646/
Hero Scenarios Link: Not Provided
Core Concepts Doc Link: Not Provided
Description: Feedback for New Api Version
Detailed meeting information and documents provided can be accessed here
For more information that will help prepare you for this review, the requirements, and office hours, visit the documentation here

Notes from API Review 5/8/24

Large breaking change
Need to update the descriptions on the new endpoints
solutions:create-job - send a request to a solution and get the response

Returns a 202 -- response body should be a status monitor

Some concern about custom authorization mechanisms
Response is just type: object -- customers must access solution API definitions to know the shape of the response
Some of these APIs will be replaced with Fabric APIs before GA

Catalogs, Collections, Items, Schemas (check?) will GA, rest will remain in preview and eventually drop
All these were reviewed previously

We won't review the non-GA endpoints in detail as they'll be dropped

This API (the parts targeted for eventual GA) looks fine for preview.

authors: azure-sdk mikekistler

repo: Azure/azure-rest-api-specs


text:
Add Java SDK

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of “no breaking changes
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Please follow the link to find more details on PR review process.

/azp run automation - sdk

/azp run unifiedPipeline

/azp run automation - sdk

authors: AutorestCI mbialecka zhenglaizhang


text:
Azure Health Bot MSI support

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[x] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[x] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[x] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

Changes looks good, please follow the process given @ https://dev.azure.com/azure-sdk/internal/_wiki/wikis/internal.wiki/212/Swagger-PR-Review to continue

@PhoenixHe-msft could you help take a look at the PS generation failure https://github.com/Azure/azure-rest-api-specs/pull/14787#issuecomment-860213077?

@dolauli Would you please help on the PS failure?

@dolauli Can you please help with the PS failure? We would like to merge this PR by the end of the month. Thanks.

ping @dolauli

/azp run

Now all validations are good, and ARM signed off. the PR LGTM.
@guy-microsoft are you fine to merge the PR? If not please put DoNotMerge label and remove it when it's fine to merge.

@zhenglaizhang Yes, please merge it if you can. Thanks.

authors: PhoenixHe-msft chiragg4u dolauli guy-microsoft zhenglaizhang


text:
[resouces] fix operation id

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

will be fixed in https://github.com/Azure/azure-rest-api-specs/pull/18692/files


text:
Updating Microsoft.Maps/DataRegistry from version preview/2.0 to stable/2022-12-01

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[x] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month. > December 2022
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month. > December 2022
If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[x] No refresh required for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[x] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

GET /mapData

If this operation supports paging (likely), then a nextLInk property must be in the response body.

POST /mapData

We very strongly prefer resources to be created with PUT or PATCH; not POST. And I see that this is an LRO creation too. Please see our new/improved guidelines for how this should be accomplished: https://github.com/microsoft/api-guidelines/blob/6d6be125cb1c6b3569795ef719f5d326e935d095/azure/Guidelines.md#long-running-operations--jobs

GET /mapData/{udid}

I don't see an example of the response payload

PATCH /mapData/{udid}

PATCH requests are not allowed for long-running; use POST-action instead. See the guidelines I linked to above.

PUT /mapData/{udid}

I see you have this PUT operation. So, just get rid of POST /mapData and use this making it an LRO that follows our guidelines.

GET /mapData/{udid}/metadata

Do you need this operation? Can't the metadata just be returned with the response from GET /mapData/{udid}?
Also, the response has a mapData property; not a metadata property - I feel like something is misplaced here

GET /mapData/operations/{operationId}

The status monitor (response payload) doesn't look right. Please follow the guiidelines I link to above.

@JeffreyRichter Thanks for your review. The new LRO guideline is super helpful, and I have fixed most of the points you mentioned. But here I have 3 follow-up questions I would like to ask.

We generate udid for our customers and they are not allowed to generate udid by themselves in our previous versions of this API. So for resource creation (Register API) in this version, we also offer them PUT /mapData instead of PUT /mapData/{udid}, which seems to me a little be inconsistent to other LRO PUT APIs. Is this acceptable from the perspective of API review board?
I cannot understand why PATCH cannot be LRO. In this service, we want to offer customers JSON Merge Patch for easier updating their resource without knowing the existing state in advance. If we don't provide LRO to them and instead, implement something like "revert if fail", they won't be able to know the reason why their PATCH request was not successful. I would like to know more why PATCH cannot be LRO and if there is other recommended way to do.
About the recommended response structure of monitor endpoint,

If the previous version of this same API required that clients cannot create the udid themselves, then keep that behavior to not break customers. If this were a new service, then we'd change this. It is not valid HTTP/REST to have PUT /mapData create a resource under mapData. If this already shipped, then keep it for back-compat; if not, then this should be removed.

PATCH is not allowed to be an LRO because an operation must either be ALWAYS LRO or NEVER LRO and this can never change over time as it is a breaking change. A resource typically has many properties and many of them can be changed synchronously and this is what PATCH is for. To change a resource via an LRO; we use POST-action. This also has the feeling of an RPC/action call which may fail where PATCH has the feeling of just changing state which should not fail. So, there are multiple reason why the POST-action LRO is better than PATCH for updating a resource. Also, the POST-action LRO can fail and give a reason for failure so I don't see any issue here.

The guidelines should have NotRunning, Running, Succeeded, Failed, and Canceled. We just discovered yesterday that NotRunning and Running were left out of the guidelines; we are adding them back in.

Thanks for clarifying the difference between GET /mapData/{udid}/metadata and GET /mapData/{udid}.

@danielthank -- In addition to @JeffreyRichter 's comments, I'd recommend running the spectral linter that we've implemented. There are a number of "cleanliness" issues this will help you clean up. For example, there are a few operations where the
Error response should contain a x-ms-error-code header.

Fixed all of the items mentioned in review board and PR review.
Some big changes:

prefix: /mapData -> /dataRegistries
GET /mapData/{udid}/metadata -> GET /dataRegistries/{udid}
GET /mapData/{udid} -> GET /dataRegistries/{udid}/content
PUT /mapData -> PUT /dataRegistries/{udid} (Register or Replace)
Utilize readOnly property so that swagger model can be simplified.

Hello @tomkerkhove, this PR is ready to merge and is open for final review

authors: JeffreyRichter danielthank markweitzel


text:
[Hub Generated] Review request for Microsoft.SqlVirtualMachine to add version preview/2022-07-01-preview

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
ARM API Information (Control Plane)
Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[x] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

@xiaoxuqi-ms we got ARM approval, can we please merge this PR?


text:
Added Azure Container Instance API Version 2024-10-01-preview

ARM (Control Plane) API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!

[ ] New resource provider.
[x] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix OpenAPI spec quality issues in S360.
[ ] Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

@MicroJamesLim Please check the comment on using "arm-id" format.

Your branch is out-of-date with base branch, please merge with base branch before requesting merge.

authors: MicroJamesLim ms-bogdan-rotaru


text:
Update Microsoft.Containerinstance swagger with DNSConfig and GPU

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] The spec follows the guidelines described in the Swagger checklist document.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-sdk-for-js

Automation for azure-sdk-for-python

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-go

Can one of the admins verify this patch?

Automation for azure-sdk-for-java

Automation for azure-sdk-for-node

Hi @xuto2 - could you please join the Azure GitHub org?

authors: AutorestCI annatisch azuresdkci xuto2


text:
Workspace: Swagger updates for CMK

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[x] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

You don't have permission to trigger SDK Automation.
Please add yourself to Azure group from opensource portal if you are MSFT employee,
or please ask reviewer to add comment *** /openapibot sdkautomation ***.
Please ask tih@microsoft.com (or NullMDR in github) for additional help.

Can one of the admins verify this patch?

Hi @DeMale I do not know if this is a good place, but I just happened to work on bringing this particular resource (MachineLearningService.Workspace) to terraform. But I found that this rest api does not work. Please have a check or we can discuss this more in an internal email.

This is a flag to mark the workspace as High Business Impact one on workspace creation. The flag to signal HBI data in the workspace and reduce diagnostic data collected by the downstream services

I strongly recommend you refine the current description of hbiWorkspace to include this information.

Hi @DeMale I do not know if this is a good place, but I just happened to work on bringing this particular resource (MachineLearningService.Workspace) to terraform. But I found that this rest api does not work. Please have a check or we can discuss this more in an internal email.

@ArcturusZhang Let's not combine other changes in this PR. We will create a separate PR for that change.

Please remove the readOnly: true for identity (here).
You can refer to this pr for details.

@ArcturusZhang Since you have a separate PR for the change requested, can we get this PR going?

Hi @DeMale I do not know if this is a good place, but I just happened to work on bringing this particular resource (MachineLearningService.Workspace) to terraform. But I found that this rest api does not work. Please have a check or we can discuss this more in an internal email.

@ArcturusZhang Let's not combine other changes in this PR. We will create a separate PR for that change.

Sure, thanks.

Hi @DeMale please let me know when you have resolved all the comments and ready to merge this pr

Hi @DeMale is this ready for merge? Or it has to wait until 01/13/2020?

Hi @ArcturusZhang It has to wait until 01/13/2020 until all the JEDI work gets into production regions.

Hi @ArcturusZhang It has to wait until 01/13/2020 until all the JEDI work gets into production regions.

Got it

/azp run

/azp run

authors: ArcturusZhang AutorestCI DeMale azuresdkci vrushg-ms


text:
Swagger updates to introduce cosmos-db api version 2020-03-01, and add PublicNetworkAccess property

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

the api ver is Mar 1 03-01, not Jan 3 01-03. Can u correct it?

/azp run automation - sdk

/azp run automation - sdk

Can one of the admins verify this patch?

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

authors: AutorestCI Liphi ayanMSFT azuresdkci


text:
Updating VpnGateway examples for bgpSettings

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[X] I have reviewed the documentation for the workflow.
[X] Validation tools were run on swagger spec(s) and have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.

adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

Can one of the admins verify this patch?

/azp run automation - sdk

authors: AutorestCI Khushboo-Baheti azuresdkci


text:
Beta JavaDoc link in use in README.md

Android JavaDoc has not published yet, so verify links will treat it as broken links. Put the link under ignore-links to skip the check temporarily. Please remember to remove it after JavaDoc link gets published.

The links have been updated to beta one. Not an issue from readme perspective. Feel free to close it if it is not that important.

Currently the javadoc on github.io is versioned - we will either not version the javadoc going forward, or we will need to automate changes to the index page.

Close the issue as it is not in the scope

authors: bsiegel sima-zhu

repo: Azure/azure-sdk-for-android


text:
Update IoT tests to import proper Powershell module versions

Versioning of the powershell modules is preventing us from being able to modify the deployed resources. Importing/installing of the modules is broken. Momentary fix unblocks the gate but we need a better long term solution.
Hotfix: https://github.com/Azure/azure-sdk-for-c/pull/1628
Long term fix (WIP): https://github.com/Azure/azure-sdk-for-c/pull/1625

Linking relevant docs:
https://github.com/Azure/azure-powershell/blob/master/documentation/troubleshoot-module-load.md#why-are-incompatibilities-possible

fixed with https://github.com/Azure/azure-sdk-for-c/pull/1694

repo: Azure/azure-sdk-for-c


text:
Docs: More details about az_log_set_classifications()

Closes #1227.
Closes #1192.
I don't think there is much more we can do for #1227.  We still can - maybe we can have a local copy of an array of some finite size, and copy elements there, but besides that I don't see much options. az_log_set_classifications() would need to return az_result in this case, if the limit is exceeded. Then, if you want more than the predefined limit, one of the options is to pass NULL to receive all classifications, and filter them out in log callback, which does receive classification in addition to message.
I had two solutions in mind:

Use mutex, and lock it when setting classifications, and while iterating over them. I do not think it is possible, given that az_log is used by IoT, and mutex is in PAL, and we don't want the dependency on PAL for the IoT scenarios.

If we know all the possible classifications, make some sort of a map of classification -> bool is_enabled, and use that internal copy; this would also have some perf benefits as side effect. But given that we now extracted IoT classifications from core into a file in the iot directory, I do not see a realistic good and simple way of doing this anymore.

I think I might give this whole idea another shot in the next sprint, I put more details in the PR description (local array copy of a finite size + returning az_result when limit is exceeded); so maybe after all we will be able to safely handle stack-allocated arrays.


text:
Investigate solutions to intermittent GTest cmake build error due to timeout from GoogleTestAddTests.cmake

This has come up from time to time, causing unrelated failures in CI. Typically, re-running the failed step passes, but we may want some sort of a built-in retry approach to improve signal-to-noise when a PR does fail in CI.
We may want to bubble this up to the GTest repo to get their advice:
https://github.com/google/googletest/issues/3475
The intermittent error is OS-agnostic.
Example: From https://github.com/Azure/azure-sdk-for-cpp/pull/3049/checks?check_run_id=4110188134
https://dev.azure.com/azure-sdk/public/_build/results?buildId=1179777&view=logs&j=e109b754-e5a4-58aa-96d5-f28daf32bc3c&t=ba4898b6-8192-5319-125f-11f9fed782cb&l=332
[ 85%] Linking CXX executable azure-security-keyvault-keys-test
CMake Error at /usr/local/Cellar/cmake/3.21.4/share/cmake/Modules/GoogleTestAddTests.cmake:77 (message):
  Error running test executable.

    Path: '/Users/runner/work/1/s/build/sdk/core/azure-core/test/ut/azure-core-test'
    Result: Process terminated due to timeout
    Output:

Call Stack (most recent call first):
  /usr/local/Cellar/cmake/3.21.4/share/cmake/Modules/GoogleTestAddTests.cmake:173 (gtest_discover_tests_impl)

https://dev.azure.com/azure-sdk/public/_build/results?buildId=1179778&view=logs&j=c58918f5-f6e3-5654-ff3d-1e867080fdaf&t=cda8dd36-518c-5d0d-6a44-b8733daa8cea&l=411
CMake Error at C:/Program Files/CMake/share/cmake-3.21/Modules/GoogleTestAddTests.cmake:77 (message):
    Error running test executable.

      Path: 'D:/a/_work/1/s/build/sdk/template/azure-template/test/Debug/azure-template-test.exe'
      Result: Process terminated due to timeout
      Output:

  Call Stack (most recent call first):
    C:/Program Files/CMake/share/cmake-3.21/Modules/GoogleTestAddTests.cmake:173 (gtest_discover_tests_impl)

cc @vhvb1989, @danieljurek

Duplicate of https://github.com/Azure/azure-sdk-for-cpp/issues/1607
Closing

repo: Azure/azure-sdk-for-cpp


text:
sdk\core\azure-core\test\libcurl-stress-test pulls the incorrect vcpkg version.

Describe the bug
The dockerfile in libcurl-stress-test\Dockerfile has the following code:
RUN wget -O vcpkg.tar.gz https://github.com/microsoft/vcpkg/archive/master.tar.gz
RUN mkdir /opt/vcpkg
RUN tar xf vcpkg.tar.gz --strip-components=1 -C /opt/vcpkg
RUN /opt/vcpkg/bootstrap-vcpkg.sh
RUN ln -s /opt/vcpkg/vcpkg /usr/local/bin/vcpkg

This code pulls what is in the current vcpkg release. But the Azure SDK is built and tested with a specific vcpkg commit (currently 94ce0dab56f4d8ba6bd631ba59ed682b02d45c46). By pulling the current baseline instead of the commit against which the packages are built, the SDK built for the Dockerfile is being built against an untested set of downstream dependencies.
Expected behavior
The dockerfile should pull the vcpkg repository at the vcpkg commit which was used to test the Azure SDK - we have had challenges when we build and test against newer vcpkg binaries.

VCPKG here runs in Manifest mode, thus it will use that version of the packages that vcpkg will use will be at that glorious SHA. E.G. when building the build logs:
Vcpkg integrate step.
CMAKE_TOOLCHAIN_FILE is not defined. Define it for the user.
AZURE_SDK_DISABLE_AUTO_VCPKG is not defined. Fetch a local copy of vcpkg.
Vcpkg commit string used: 94ce0dab56f4d8ba6bd631ba59ed682b02d45c46
-- Bootstrapping vcpkg before install

reope to use for PR update

authors: LarryOsterman gearama


text:
Adding support for libcurl version 7.4

fixes: https://github.com/Azure/azure-sdk-for-cpp/issues/1170

Closing as not to be implemented after reviewing it on stand up meeting. See previous comments for more info


text:
Sync eng/common directory with azure-sdk-tools for PR 7185

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/7185  See eng/common workflow

/check-enforcer override

authors: azure-sdk benbp


text:
OSimage get operation fails.

The osimage.Client.GetImageList() operation consistently fails with:
Get https://management.core.windows.net/<my-subscription-id>/services/images: local error: internal error

Update:
I get that for

Thanks @aznashwan
"local error" point to a transport level error (HTTPS/TLS)...
Is it just this method or all methods?
Are you using a proxy?

Hello @paulmey, and thanks for the response.
Yes, everything was returning the same 'internal server error' for me up to now.
Upon looking further into the matter, it seems the problem was on my end with the format and encoding of my certificates. Weirdly enough; it granted me access just fine but afterwards it kept yielding the above error.
It works fine with a .publishsettings file, unfortunately my application would not have much access for getting such a file too easily.
I do very much apologize for raising an issue prematurely.
Everything works fine now, and thanks a bunch for providing this sdk for us.
PS: if I could go as far as ask you specifically what certificate encoding Azure works best with?

No problem. For certificate handling, we use the 'standard' go pem/tls crypto packages, so anything that those support should work. The reason for vendoring the tls and http packages is to support a renegotiation feature that Azure needs, but is not in the upstream go libraries yet.
See https://github.com/golang/go/issues/5742 for more info...

Thank you very much, and my apologies again for all the bother.

authors: aznashwan paulmey

repo: Azure/azure-sdk-for-go


text:
Specifying Multiple IP Configurations per Network Interface

I am trying to make the following call to the API:
{
	"name": "acceptanceTestNetworkInterface1",
	"location": "westus",
	"properties": {
		"ipConfigurations": [{
			"properties": {
				"loadBalancerBackendAddressPools": null,
				"loadBalancerInboundNatRules": null,
				"privateIPAllocationMethod": "dynamic",
				"subnet": {
					"id": "/subscriptions/xxxx/resourceGroups/acceptanceTestResourceGroup1/providers/Microsoft.Network/virtualNetworks/acceptanceTestVirtualNetwork1/subnets/testsubnet1"
				}
			},
			"name": "testconfiguration2"
		}, {
			"properties": {
				"loadBalancerBackendAddressPools": null,
				"loadBalancerInboundNatRules": null,
				"privateIPAllocationMethod": "dynamic",
				"subnet": {
					"id": "/subscriptions/xxxx/resourceGroups/acceptanceTestResourceGroup1/providers/Microsoft.Network/virtualNetworks/acceptanceTestVirtualNetwork1/subnets/testsubnet"
				}
			},
			"name": "testconfiguration1"
		}],
	}
}

I get the following response:
{
	"error": {
		"code": "NetworkInterfaceMustHaveOneOneIPConfigAsPrimary",
		"message": "Network Interface acceptanceTestNetworkInterface1 specifies multiple IPConfigurations but none of the IPConfigurations is specified as Primary.",
		"details": []
	}
}

The struct for the network interface looks as follows:
type Interface struct {
	autorest.Response `json:"-"`
	ID                *string                    `json:"id,omitempty"`
	Name              *string                    `json:"name,omitempty"`
	Type              *string                    `json:"type,omitempty"`
	Location          *string                    `json:"location,omitempty"`
	Tags              *map[string]*string        `json:"tags,omitempty"`
	Properties        *InterfacePropertiesFormat `json:"properties,omitempty"`
	Etag              *string                    `json:"etag,omitempty"`
}

type InterfacePropertiesFormat struct {
	VirtualMachine       *SubResource                `json:"virtualMachine,omitempty"`
	NetworkSecurityGroup *SecurityGroup              `json:"networkSecurityGroup,omitempty"`
	IPConfigurations     *[]InterfaceIPConfiguration `json:"ipConfigurations,omitempty"`
	DNSSettings          *InterfaceDNSSettings       `json:"dnsSettings,omitempty"`
	MacAddress           *string                     `json:"macAddress,omitempty"`
	Primary              *bool                       `json:"primary,omitempty"`
	EnableIPForwarding   *bool                       `json:"enableIPForwarding,omitempty"`
	ResourceGUID         *string                     `json:"resourceGuid,omitempty"`
	ProvisioningState    *string                     `json:"provisioningState,omitempty"`
}

The Primary is outside of the IPConfigurations. Therefore, we cannot pass primary: true for any of the IPConfigurations. The correct request should look as follows:
{
	"name": "acceptanceTestNetworkInterface1",
	"location": "westus",
	"properties": {
		"ipConfigurations": [{
			"properties": {
				"loadBalancerBackendAddressPools": null,
				"loadBalancerInboundNatRules": null,
				"privateIPAllocationMethod": "dynamic",
				"subnet": {
					"id": "/subscriptions/xxxx/resourceGroups/acceptanceTestResourceGroup1/providers/Microsoft.Network/virtualNetworks/acceptanceTestVirtualNetwork1/subnets/testsubnet1"
				}
			},
			"name": "testconfiguration2"
		}, {
			"properties": {
				"loadBalancerBackendAddressPools": null,
				"loadBalancerInboundNatRules": null,
				"privateIPAllocationMethod": "dynamic",
				"subnet": {
					"id": "/subscriptions/xxxx/resourceGroups/acceptanceTestResourceGroup1/providers/Microsoft.Network/virtualNetworks/acceptanceTestVirtualNetwork1/subnets/testsubnet"
				}
                                "primary": true
			},
			"name": "testconfiguration1"
		}],
	}
}

I haven't looked into the Swagger yet but can verify the structures in the generated client do not match what is running in production, and it is therefore impossible to create a network interface with multiple IP configurations without hacking around the SDK at present - for now we've just documented it as a bug in the Terraform docs, and will update when this is fixed.

The issue comes from the Swagger. I've verified that it is in both the Network/2015-06-15 and prior version. See https://github.com/Azure/azure-rest-api-specs/blob/master/arm-network/2015-06-15/swagger/network.json#L5849.
If you would not mind, please, post an issue against that repository. I'll poke around as well.

Hi @stack72,
Thanks for pointing this out. The "primary" flag outside IPConfiguration is valid since we support MultiNic scenario. So the flag will tell the user whether the nic is a primary or not.
Yes, though we have IPConfiguration as a list, we are currently working on Multiple IPConfiguration support (once that is done, we will update the schema and the client with the "primary" field). This currently is a bug on the service where we are not throwing the appropriate error message. (the message should be something along the lines of "Multiple IPConfigurations not supported"). We will fix this soon.
Thanks,
Deepak.

@DeepakRajendranMsft
I don't understand. When I query for my NIC in resources.azure.com, I can see the ipConfiguration itself has a primary field that is populated.
On the other hand, when I query my VM and inspect the NetworkProfile, the Primary field is NOT populated on the interface.
This indicates to me that the Swagger does not conform to the actual behavior of the API. I'm actively having to work around this by making certain assumptions.

GET https://management.azure.com/subscriptions/27b750cd-ed43-42fd-9044-8d75e124ae55/resourceGroups/colemick-kube-ubuntu-0/providers/Microsoft.Compute/virtualMachines/master?api-version=2016-03-30

[...]
    "networkProfile": {
      "networkInterfaces": [
        {
          "id": "/subscriptions/27b750cd-ed43-42fd-9044-8d75e124ae55/resourceGroups/colemick-kube-ubuntu-0/providers/Microsoft.Network/networkInterfaces/master815"
        }
      ]
    },
[...]

So this does not contain the `primary` field, despite the Swagger spec saying that it would.

And then:

GET https://management.azure.com/subscriptions/27b750cd-ed43-42fd-9044-8d75e124ae55/resourceGroups/colemick-kube-ubuntu-0/providers/Microsoft.Network/networkInterfaces/master815?api-version=2016-03-30
[...]
"ipConfigurations": [
{
"name": "ipconfig1",
"id": "/subscriptions/27b750cd-ed43-42fd-9044-8d75e124ae55/resourceGroups/colemick-kube-ubuntu-0/providers/Microsoft.Network/networkInterfaces/master815/ipConfigurations/ipconfig1",
"etag": "W/"fdea6b24-7abe-4f57-986e-c27e14eff876"",
"properties": {
"provisioningState": "Succeeded",
"privateIPAddress": "10.0.0.4",
"privateIPAllocationMethod": "Dynamic",
"publicIPAddress": {
"id": "/subscriptions/27b750cd-ed43-42fd-9044-8d75e124ae55/resourceGroups/colemick-kube-ubuntu-0/providers/Microsoft.Network/publicIPAddresses/master"
},
"subnet": {
"id": "/subscriptions/27b750cd-ed43-42fd-9044-8d75e124ae55/resourceGroups/colemick-kube-ubuntu-0/providers/Microsoft.Network/virtualNetworks/colemick-kube-vnet/subnets/colemick-kube-nodes"
},
"primary": true,
"privateIPAddressVersion": "IPv4",
"loadBalancerBackendAddressPools": [
{
"id": "/subscriptions/27b750cd-ed43-42fd-9044-8d75e124ae55/resourceGroups/colemick-kube-ubuntu-0/providers/Microsoft.Network/loadBalancers/aafdf4dfe1a8b11e6a4f2000d3a332e1/backendAddressPools/aafdf4dfe1a8b11e6a4f2000d3a332e1"
}
]
}
}
[...]

Which shows the ipConfiguration coming back with a "primary" field, and yet this isn't exposed in Swagger.

The net result is that I can't tell which NIC is primary, **and** I can't tell which ipConfiguration on a given NIC is primary. This does not seem correct to me.

@colemickens do you know if this is fixed?

Not really. The other thread: https://github.com/Azure/azure-rest-api-specs/issues/305 has open questions about if this has been addressed appropriately. I'll ping that thread.

This is resolved. See here for the details: https://github.com/Azure/azure-rest-api-specs/issues/305#issuecomment-239336420

authors: DeepakRajendranMsft ahmetalpbalkan brendandixon colemickens jen20 stack72


text:
Failed to delete resource NetApp Pool when the delete API of NetApp Volume returns 404

Bug Report

Import path of package in question: https://github.com/Azure/azure-sdk-for-go/tree/master/services/netapp/mgmt/2019-06-01/netapp
SDK version: v35.0.0
Output of go version: go version go1.12.7 windows/amd64

What happened?
The resource NetApp Volume depends on the resource NetApp Pool. Although the delete API returns 404 which means the NetApp Volume resource has been deleted. Then it tries to immediately delete NetApp Pool but it still throws error Can not delete resource before nested resources are deleted., which means the resource NetApp Volume still hasn't been deleted. So it failed to delete top resource NetApp Pool.

What did you expect or want to happen?
It should delete both resources NetApp Volume and NetApp Pool successfully.

How can we reproduce it?

Create a resource group
Create NetApp Account
Create NetApp Pool
Create NetApp Volume
Delete NetApp Volume, which returns "202"
Immediately call "Get" rest api to get resource NetApp Volume, which returns "404"
Immediately delete NetApp Pool, which returns error code "409"
Then it throws error Can not delete resource before nested resources are deleted.

Anything we should know about your environment.
The error message:
"Error: Error deleting NetApp Pool "acctest-NetAppPool" (Resource Group "acctestRG-netapp"): netapp.PoolsClient#Delete: Failure sending request: StatusCode=0 -- Original Error: autorest/azure: Service returned an error. Status= Code="CannotDeleteResource" Message="Can not delete resource before nested resources are deleted."" when the delete API of NetApp Volume returns 404.

Hi @leonardbf could please help on this issue?

I am also receiving an error while deleting a ANF volume from Azure portal. The error message is as below.
Can not delete resource before nested resources are deleted.

Did this ever get resolved? Having a similar issue.

We have retired support for Azure SDK for Golang libraries which do not conform to our current Azure SDK guidelines (see announcement). Please migrate to the latest version according to the migration guide. If you could still repo this problem, please submit a support ticket in Azure directly.

authors: ArcturusZhang devtrf neil-yechenwei prasroy tadelesh


text:
Automatic PR of restapi_auto_lmazuel_eventgrid_Data into dev

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/2369

Closing for now, in response to #1057. These changes will be incorporated shortly.

authors: AutorestCI marstr


text:
[AutoPR securityinsights/resource-manager] chore: jsonfmt securityinsights

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/6331

This PR has been merged into https://github.com/Azure/azure-sdk-for-go/pull/5020


text:
Support Spark Filter to Cosmos Query Predicate Pushdown

Support translating Spark Filter to Cosmos DB Query Predicates.

implemented in this PR: https://github.com/Azure/azure-sdk-for-java/pull/17789

repo: Azure/azure-sdk-for-java