text:
[ARM] az deployment: Fix parse errors with multiline strings

Description
For more complex multiline strings (such as policies for Azure API Management), az deploy will fail with message:  Failed to parse ... , please check whether it is a valid JSON format, because multiline string contains block quotes within the string.
This PR adds test case that's failing with current az and naive proposal to improve detection of such situation. I couldn't find a regexp that is solving all cases, that's why I just slightly changed existing one and added check with replacement. The regex is already quite complex and I think it's already on the bridge of being understandable.
Testing Guide
Test cases are provided within PR.
History Notes
[resource] Fix parsing JSON files with multi-line strings

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

resource

Related issue: #12909

@wiktorn Hi, thank you for your contribution.
However, there are still some problems with the support of service for multi-line, the verification of CLI pass multi-line still can't solve the problem.

If it is multi-line of pure describing text, service will break the original format with newline character. For example:

In ARM template:

"meta": {
    "type": "string",
    "metadata": {
        "description": "meta of the network security group."
    },
    "defaultValue": "ARM
    template
    test
    newline"
}

After service processing:

"meta": {
    "type": "String",
    "value": "ARM\r\n      template\r\n      test\r\n      newline"
}

If it is multi-line of parameter values, service may break the resolution of those values.
For example:

"defaultValue": "
    [resourceGroup().location]
"

It will cause an error in the service:
{"error":{"code":"InvalidResourceLocation","message":"The specified location '\r\n        [resourceGroup().location]\r\n      ' is invalid. A location must consist of characters, whitespace, digit, or following symbols '(,)'."}}

Please refer to this issue #12909 for the discussion of the service problem.
I suggest that this PR should not merge at this time. After the service solves this problem, this PR can be merged to pass the verification of multi-line in CLI side.

I gave this second thought and I thing that maybe the best approach to this problem is to use custom json decoder (lets call it azjson) that would respect the rules for Resource templates (comments allowed, multiline strings allowed). Is there any chance to use the same algorithm on both ends?
If such tool would be written, then following template:
"meta": {
    "type": "string",
    "metadata": {
        "description": "meta of the network security group."
    },
    "defaultValue": "ARM
    template
    test
    newline"
}`

Would indeed have in-memory representation as:
"meta": {
    "type": "String",
    "value": "ARM\r\n      template\r\n      test\r\n      newline"
}

(modulo platform discrepancies around CRLF/CR).
Also - taking a look into the json module, maybe far easier approach than this regex magic would be just to pass strict=False argument to json parser in shell_safe_json_parse? The difference would be, that other control characters would be allowed within template.

@wiktorn Hi, may I ask what should we do if the multi-line is in the value of parameters?
Such as:
"defaultValue": "
    [resourceGroup().location]
"

If it is translated to
defaultValue": "\r\n        [resourceGroup().location]\r\n      "

, the parsing of this value should be destroyed.
And another factor is that in our design, CLI can't modify the user's template, so it needs to send the template directly to the Service.

@wiktorn Hi, may I ask what should we do if the multi-line is in the value of parameters?
Such as:
"defaultValue": "
    [resourceGroup().location]
"

With such templates - do noting. Pass it to Service, and if it will be rejected there - it's perfectly fine as the message is clear (location should not contain whitespace characters) and user can easily fix.
As I understand, you would like multiline strings behave something like that (example in Python):
defaultValue = "" +
    "[resourceGroup().location]" +
    ""

But even multiline strings in Python do not behave that way and maintain all the whitespace even though it has semantic meaning in language and for example - all it is possible to remove whitespace that was used to indent nearby code. But this was only implemented (as post-processing) to docstrings. So I think that Pythons strategy with multiline strings is perfectly fine here too and it's still in line with the documentation. AFAIR there is nothing there, that some magic with whitespace will happen.
Or maybe I'm just totally not understanding the problem that you raise with this. My assumptions are:

such template fails on Service, because location contains invalid characters
there is no implementation of ARM Template functions, so cli doesn't parse the value

such template fails on Service, because location contains invalid characters

Yes, the value cannot be parsed properly because it contains invalid characters, such as \r\n      .

As I see no follow-up on #12909, can we proceed with this one? Would you like to stay with this approach or you prefer to go with json.load(..., strict=False) ?

Let me try to contact the service team again. I have just summarized the questions into an email to ask them

@zhoxing-ms any updates on this?

@wiktorn Hi, as we discussed with the Service team, the current behavior of the service is in line with expectations, so we only need to merge this PR to solve the CLI verification problem (If you are interested in the details of our communication, I can forward the email to you~)

I've created the branch with the other approach (non-strict JSON parsing) which doesn't need any magic regexes:
https://github.com/Azure/azure-cli/compare/dev...wiktorn:multiline_string_nonstrict_parse?expand=1
If you'd still want to continue with present approach, I've added comments with description how this regex works.

Shall I rebase it on dev? There are conflicts in recordings, as I've recorded them using WSL, also - not sure what is the policy to provide them.
OTOH, as far as I see, there are some other tests failing currently on dev.

I've created the branch with the other approach (non-strict JSON parsing) which doesn't need any magic regexes:
https://github.com/Azure/azure-cli/compare/dev...wiktorn:multiline_string_nonstrict_parse?expand=1
If you'd still want to continue with present approach, I've added comments with description how this regex works.

It's a nice solution ! I think it's more readable and easier to maintain~
Could you please use it to update this PR?

Shall I rebase it on dev? There are conflicts in recordings, as I've recorded them using WSL, also - not sure what is the policy to provide them.
OTOH, as far as I see, there are some other tests failing currently on dev.

Yes, you need to fetch the latest code from the remote dev branch, then rebase locally before committing this PR

Code rebased, changed approach to non-strict json parsing.
I haven't updated the test recordings, not sure what to do about that.

Code rebased, changed approach to non-strict json parsing.
I haven't updated the test recordings, not sure what to do about that.

@wiktorn In fact, you need to rerun the test azdev test test_resource_group_deployment --live in live mode and then upload the updated yaml file.

authors: wiktorn yonzhan zhoxing-ms


text:
{Core} Show custom headers

When making any HTTP request, CLI will add some custom headers

x-ms-client-request-id
CommandName
ParameterSetName

to the request via the SDK client. But msrest doesn't print custom headers in the debug log.
This PR makes CLI print custom headers so that users can know what information is sent to the server and logged in the server-side telemetry. This can also help code-gen team gather more information without checking the server-side telemetry.
> az group show -n fy --debug

Adding custom headers to the client:
    'x-ms-client-request-id': '220893a8-14e0-11eb-ae06-84a93e63aa78'
    'CommandName': 'group show'
    'ParameterSetName': '-n --debug'
...
msrest.http_logger : Request URL: 'https://management.azure.com/subscriptions/0b1f6471-1bf0-4dda-aec3-cb9272f09590/resourcegroups/fy?api-version=2020-06-01'
msrest.http_logger : Request method: 'GET'
msrest.http_logger : Request headers:
msrest.http_logger :     'Accept': 'application/json'
msrest.http_logger :     'accept-language': 'en-US'
msrest.http_logger :     'User-Agent': 'python/3.8.6 (Windows-10-10.0.19041-SP0) msrest/0.6.18 msrest_azure/0.6.3 azure-mgmt-resource/10.2.0 Azure-SDK-For-Python AZURECLI/2.13.0 (PIP)'

ℹ Track 2 SDK can print custom headers correctly, so there is no need to do this in configure_common_settings_track2.

Does CLI allow users to add their own headers? Will those self defined headers show up when using --debug ?

Core

Does CLI allow users to add their own headers? Will those self defined headers show up when using --debug ?

Currently there is no such parameter for custom headers.

/azp run

source: gharchive/pull-request

authors: jiasli qiaozha yonzhan

repo: Azure/azure-cli

license: MIT

license_type: permissive

license_source: github-api


text:
[Storage] Fix #23262: az storage blob metadata: Add --lease-id back

Related command

az storage blob metadata show/update
Description

Fix #23262
--lease-id was missing during track2 migration for az storage blob metadata

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Storage

authors: evelyn-ys yonzhan


text:
{Backup} Add new secondary region pairings

Related command

az backup
Description

Updated the paired region map that allows for Cross-Region Restore operations in Azure Backup
Testing Guide

No testing required - verified earlier on the service side.
History Notes

Updated the paired region map that allows for Cross-Region Restore operations in Azure Backup

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

Backup

Can we run the test suite again, if it's been fixed?

Can we run the test suite again, if it's been fixed?

Done

authors: yonzhan zhoxing-ms zubairabid


text:
{Compute} Update vm test with new versioned image aliases

Related command

az vm image
Description

Update vm tests with old versioned image alias because in Ignite (November) 2023, the aliases without version suffix (such as: UbuntuLTS, CentOS, Debian, Flatcar, SLES, openSUSE-Leap and RHEL) will be removed.
relatedPRs:
https://github.com/Azure/azure-cli/pull/26483
https://github.com/Azure/azure-cli/pull/25930
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Compute


text:
[Service Fabric] add upgradeType property

Related command

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Service Fabric

authors: mwesigwaguma yonzhan


text:
Adding functionality for Virtual Network Rules (Vnet)

This change adds functionality for the feature - Virtual Network Rules.
az sql server vnet-rule commands are -
create: Creates or updates an existing virtual network rule.
delete: Deletes the virtual network rule with the given name.
list  : Gets a list of virtual network rules in a server.
show  : Gets a virtual network rule.
update: Updates a virtual network rule.

This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines

[x] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

Command Guidelines

[x] Each command and parameter has a meaningful description.
[x] Each new command has a test.

(see Authoring Command Modules)

@dnayantara,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

Also, please run check_style --module sql --pep8 --pylint and fix any linter errors to get the PR green.

The build seems to be failing because of an error in
ERROR: test_aad_admin (azure.cli.command_modules.sql.tests.test_sql_commands.AzureActiveDirectoryAdministratorScenarioTest)

Output of az sql server vnet-rule create -h
Command
az sql server vnet-rule create: Creates or updates an existing virtual network rule.
Arguments
--name -n           [Required]: The name of the virtual network rule.
--resource-group -g [Required]: Name of resource group. You can configure the default group
using az configure --defaults group=<name>.
--server -s         [Required]: The name of the server.
--vnet-subnet-id -v           : The resource ID of the virtual network subnet.
Global Arguments
--debug                       : Increase logging verbosity to show all debug logs.
--help -h                     : Show this help message and exit.
--output -o                   : Output format.  Allowed values: json, jsonc, table, tsv.
Default: json.
--query                       : JMESPath query string. See http://jmespath.org/ for more
information and examples.
--verbose                     : Increase logging verbosity. Use --debug for full debug logs.

Server AD Admin test requires a fix in python SDK. This is part of https://github.com/Azure/azure-sdk-for-python/pull/1413

@jaredmoo I saw that your PR was merged. What do I need to do here to get this merged?

tasks remaining:

[ ] Jared - final testing of merged changes
[ ] Laurent - publish sdk
[ ] Jared - send PR to update azure-cli with new sdk, get it reviewed and merged into master
[ ] Nayantara - resolve merge conflicts, then we can merge this PR

My PR to update SDK is https://github.com/Azure/azure-cli/pull/4403 . Nayantara I have merged this with your code in my branch https://github.com/jaredmoo/azure-cli/tree/sqlvnet , but to prevent confusion let's wait for my PR to be merged before updating yours.

#4403 is merged so you should be able to rebase and hopefully the CI will pass.

Lingering linter errors.

Codecov Report

Merging #4343 into master will increase coverage by 0.06%.
The diff coverage is 86.66%.

@@            Coverage Diff             @@
##           master    #4343      +/-   ##
==========================================
+ Coverage   69.06%   69.12%   +0.06%
==========================================
  Files         484      493       +9
  Lines       31112    31483     +371
  Branches     4854     4905      +51
==========================================
+ Hits        21486    21763     +277
- Misses       8043     8126      +83
- Partials     1583     1594      +11

Impacted Files
Coverage Δ

...ure-cli-sql/azure/cli/command_modules/sql/_util.py
91.42% <100%> (+0.51%)
:arrow_up:

...ure-cli-sql/azure/cli/command_modules/sql/_help.py
100% <100%> (ø)
:arrow_up:

...re-cli-sql/azure/cli/command_modules/sql/params.py
97.1% <100%> (+0.07%)
:arrow_up:

...-cli-sql/azure/cli/command_modules/sql/commands.py
99% <100%> (+0.08%)
:arrow_up:

...re-cli-sql/azure/cli/command_modules/sql/custom.py
87.59% <63.63%> (-1.07%)
:arrow_down:

src/azure-cli-core/azure/cli/core/util.py
66.04% <0%> (-2.99%)
:arrow_down:

...azure-cli-core/azure/cli/core/commands/__init__.py
67.79% <0%> (-2.92%)
:arrow_down:

src/azure-cli-core/azure/cli/core/_help.py
55.78% <0%> (-0.21%)
:arrow_down:

...on/azure/cli/command_modules/extension/commands.py
100% <0%> (ø)

...li-extension/azure/cli/command_modules/__init__.py
100% <0%> (ø)

... and 10 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9d75e7a...da1500f. Read the comment docs.

authors: codecov-io dnayantara jaredmoo msftclas tjprescott


text:
Update on Installing SQL Server topic

I had to add a FWLink to the Virtual Machine sizes topic in this topic for IAAS GA. Thanks for your help!

@Selcin Thank you for raising this issue.  We're closing old issues.  If you feel this issue should remain open, please comment to let us know that the issue should be reopened.

source: gharchive/issue

authors: Selcin deneha

repo: Azure/azure-content


text:
[Question] When will the Terraform support feature go live?

Hi Team,
Good day!
I want to use Terraform with Azure Developer CLI tools to deploy my Web App. I am also aware that Terraform features are in the beta version. However, I would like to inquire, when will the Terraform support feature go live?
Terraform features are in the beta version
Thanks in advance!

Terraform support is live in product today. We don't have a definite timeline for advancing it to stable or GA. Advancement depends on usage and feedback.

@cryanskl - Have you tried the Terraform implementation yet?  We'd be curious to get some feedback from you and see if there's anything about it that needs to be improved.  Thanks

authors: cryanskl jongio savannahostrowski

repo: Azure/azure-dev


text:
Func apps are being reset after re-provision

Run azd up on project with function
Test that the function is working
Run azd provision
Try to hit the function
It won't be available, because the "re-provision" after a deploy removes the code from the function.

Could be related to this: https://stackoverflow.com/questions/59740162/azure-function-code-deleted-after-a-new-arm-deployment-from-azure-devops

@vhvb1989 @jongio  given we have added azd provision to skip if no deltas are found. Function app shouldn't get reset.
But with a forced provisioning using azd provision --no-state I am able to see the web and the service accessible. Tried with azd init -t todo-python-mongo-swa-func. Please reopen if you find issues.


text:
Fail to run command azd up

Describe the issue:
For all todo templates, running the command azd up failed with the following error message today:
Notes: There was no such issue two days ago.

Repro Steps:

Login in with command: azd auth login.
Run command: azd init -t todo-nodejs-mongo-aks -b staging.
Run command azd up.

Environment:

Template: all todo templates (under azure-dev).
Branch: pr/3976 and staging.
OS: Windows, Codespaces, Devcontainer, Linux, Mac.
Azd version: azd version 1.10.0-beta.1-daily.3947259 (commit 5bf8568b1566723be8bc2259c578df4f931cf430).

Expected behavior:
The command azd up can be run successfully.
@jongio for notification.

Does this happen with 1.9.4?

This may have been transient.  Please re-test

Based on the azd 1.9.4 version test, this issue still exists.

This may have been transient. Please re-test

We retested today and still have this issue. Application insights cannot be created normally.

This issue still exists in eastus. After changing a location (such as westus), this issue no longer exists.

@rajeshkamal5050 or @weikanglim @vhvb1989 What do you think we should do here?

@Menghua1 Can you try retesting it again to see if anything changes? I'm wondering if this was a blip in the service, since iur CI runners are running azd up successfully in eastus2. I just tried this morning and it worked fine as well:

It seems that the ARM deployment worker -> app insight request is failing, so it shouldn't be anything that azd has control over on the client-side.

CI runners are running

@weikanglim , IIRC, we don't run aks template in CI.  Did we change that?

nvm @weikanglim , I just noticed I am mixing this issue and https://github.com/Azure/azure-dev/issues/4108#issuecomment-2226283947 , LOL.  (b/c this issue is mentioning aks on the description).
But you are right, this looks like a blip in the service

@weikanglim We retested it, this issue did not reoccur in eastus2.


text:
Feature Request - Support for a post provision script.

It would be beneficial for azd to support a post provision script.
For example -
In my Bicep, I define a resource for an Azure Postgres DB and my application once deployed assumes that the table for that DB already exists. I cannot create the table in the Bicep due to the RP not supporting the capability.  So I need to run a custom command to create the script in between an azd provision and an azd deployment.
It would be great if azd up could be aware of the post provision script as well so I can provision/deploy in a single command and everything is operational.

That is possible...but ...
ARM deployment scripts require

storage account
user defined managed identity

Storage account is not required; the script can be provided inline in Bicep via scriptContent property
Some identity/credentials are required depending what resources the script is supposed to manipulate. For Azure resources, it can use a user-defined managed identity via identity property, but one can also pass credentials to the script and have it log in via Azure CLI. The latter may be handy if the deployment is already creating some identities for the application access.
That said, database initialization is a very common requirement, and the script can use whatever authN method the database supports; it does not have to be user-defined managed identity.

This exists now - closing

authors: greenie-msft jongio karolz-ms savannahostrowski


text:
vs-server: Add progress message when analyzing Aspire app while creating environment

Add a progress message to improve the UX slightly.

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/3747/uninstall-azd.sh | bash;
curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3747/install-azd.sh | bash -s -- --base-url https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3747 --version '' --verbose --skip-verify

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

Windows
PowerShell install
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3747/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/3747/install-azd.ps1' > install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3747' -Version '' -SkipVerify -Verbose;"

MSI install
powershell -c "irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3747/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/3747/azd-linux-amd64.tar.gz
ARM64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3747/azd-linux-arm64.tar.gz

MacOS -

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

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

MSI

https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3747/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/18/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


text:
Add CSharp Azure SQL to well-known templates list

Position on the list (last entry) was vetted by @savannahostrowski

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/610/uninstall-azd.sh | bash;
curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/610/install-azd.sh | bash -s -- --base-url https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/610 --version '' --verbose

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

Windows
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/610/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/610/install-azd.ps1' > install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/610' -Version '' -Verbose;"

Standalone Binary

Linux - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/610/azd-linux-amd64.tar.gz
MacOS - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/610/azd-darwin-amd64.zip
Windows - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/610/azd-windows-amd64.zip

Container
docker run -it azdevcliextacr.azurecr.io/azure-dev:pr-610

authors: azure-sdk karolz-ms


text:
yum check-update?

Why have the check-update? If the azure-cli requires something it will grab the update as part of the yum install or yum update command. yum check-update will just list other available updates on the system.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f9f55d23-7802-e0da-6d12-b71f6da8a1d4
Version Independent ID: 192846d7-baae-bcba-698b-22bdcdae468a
Content
Content Source
Service: multiple

Thanks for the report, this part of the instructions has been removed now.

authors: sptramer vincepower

repo: Azure/azure-docs-cli-python


text:
Connect-AzureAD requires elevated shell when authenticating with a service principal and certificate

Hello,
Not sure if this is intentional but it appears that an elevated shell is required to connect to AzureAD when using a service principal and certificate. Authenticating with -AadAccessToken and -AccountId works fine in a normal shell, as does logging in interactively with Connect-AzureAD.
I thought maybe when trying to retrieve to certificate thumbprint from the localmachine cert store, but that works fine as well without an elevated prompt.
Hopefully I'm just missing something on my end but thought I'd open a request anyways.
Thanks!
Here are the errors that I get:
Connect-AzureAD : One or more errors occurred.
At line:5 char:1
+ Connect-AzureAD -TenantId $tenantID -ApplicationId $applicationID -Ce ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : AuthenticationError: (:) [Connect-AzureAD], AggregateException
    + FullyQualifiedErrorId : Connect-AzureAD,Microsoft.Open.Azure.AD.CommonLibrary.ConnectAzureAD

Connect-AzureAD : Keyset does not exist

At line:5 char:1
+ Connect-AzureAD -TenantId $tenantID -ApplicationId $applicationID -Ce ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : AuthenticationError: (:) [Connect-AzureAD], CryptographicException
    + FullyQualifiedErrorId : Connect-AzureAD,Microsoft.Open.Azure.AD.CommonLibrary.ConnectAzureAD

Connect-AzureAD : One or more errors occurred.
At line:5 char:1
+ Connect-AzureAD -TenantId $tenantID -ApplicationId $applicationID -Ce ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Connect-AzureAD], AggregateException
    + FullyQualifiedErrorId : System.AggregateException,Microsoft.Open.Azure.AD.CommonLibrary.ConnectAzureAD```

Can confirm the exact same behaviour - thanks for the workaround of running as admin.

You don't need an elevated shell. You just need to give the account permission to read the private key which it doesn't have by default (unless you happen to be an admin with an elevated shell).
Here's a StackOverflow question that describes how to configure permissions for the NETWORK SERVICE account. But you can apply the information to any account or group that needs access.
https://stackoverflow.com/questions/46964941/service-fabric-authenticating-with-azure-keyvault-via-cert-keyset-does-not-ex

If the certificate/private key is only going to be accessed by a single user (yourself or a service code running a scheduled task for example) then you can simply store them in the user's own personal certificate store to which that user has full rights. In fact if this is the case, I think I'd say that's more secure as it's not available to other users (at least, not as easily).
If you have a PFX of the cert/key and you're logged in as the user who's store you want to put it in then you can just double-click it to import.
However, if you're not currently logged in as the user who's store you want to add it to you can spin up a PowerShell prompt/ISE  session as the user (shift+right-click run as different user) then run the following (you can use this instead of double-clicking above too):
$pwd = Read-Host -Prompt "Password" -AsSecureString Import-PfxCertificate -FilePath C:\path\to\file\filename.pfx -CertStoreLocation Cert:\CurrentUser\My -Password $pwd

This is resolved.

authors: andypturner benkd billmath clownwilleatme rmbolger

repo: Azure/azure-docs-powershell-azuread


text:
mcr.microsoft.com/azure-functions/python:4-python3.10-slim vulnerably

Hi,
We are using the following Azure Function Python docker image for our application on AKS: mcr.microsoft.com/azure-functions/python:4-python3.10-slim.
This is the latest image that I can find on docker: https://hub.docker.com/_/microsoft-azure-functions-python. However, we noticed that the image contains a lot of vulnerability when we performed a vulnerability scan using Trivy.
Do you know if this is a known issue, and do you know if Microsoft will be providing a more up to date docker image for Azure Function Python soon?

@georgesterian Also we could observe sonar vulnerabilities in the default docker image generated. Wondering if the Microsoft team will address the issue?

same in our case, any further advice?

authors: georgesterian slbin sudharsan2020

repo: Azure/azure-functions-docker


text:
Add an interface for the HTTP response

We should add a TypeScript interface for an HTTP response object. This gets tricky because we support both express-like and http-module-like ways of crafting a Response.
See discussion here:
https://github.com/Azure/azure-functions-nodejs-worker/pull/160

Would love this! Also, FYI, currently the response object is defined as optional which seems to be incorrect according to discussion in #160. It misleading suggests that if (!context.res) { ... } is a valid way to check if a response has been set, which isn't.

@IGx89 - the response object is optional because in non-HTTP scenarios, there is no context.res (ex: functions that are queue-triggered, cosmos DB-triggered, event grid-triggered, etc.). But you are right that the res object is always there for HTTP scenarios (which is most common for JS developers), and that function code should never be checking if (context.res)

Ha, good point! Completely forgot about the non-HTTP scenarios. If you don't mind me asking here, what is the proper way to check if an HTTP response (context.res = {}) has already been set or not?

@IGx89 - the response object is optional because in non-HTTP scenarios, there is no context.res (ex: functions that are queue-triggered, cosmos DB-triggered, event grid-triggered, etc.). But you are right that the res object is always there for HTTP scenarios (which is most common for JS developers), and that function code should never be checking if (context.res)

Is there a reason we're not considering interface inheritance for this?
As an aside, perhaps this is a bit of a design smell around the abstraction function bindings are attempting to provide.

@mhoeger do you have an update on this item?

According to the docs the res interface should have body, headers, isRaw, status, and cookies.
Would be great to get an interface for this landed to compliment HttpRequest - even if it needs interaction, having an interface would serve as a starting point.
(also, in my testing I've found that statusCode works too)

Partially addressed in #529. Closing this issue in favor of #551

authors: G-Rath IGx89 ShawnTalbert fabiocav hossam-nasr mhoeger

repo: Azure/azure-functions-nodejs-worker


text:
Upgrade version of Microsoft.Azure.WebJobs.Extensions.Http to remove vulnerability

There is a vulnerability in Microsoft.AspNetcore.Http in 2.1.0 that we need to upgrade
References:

https://github.com/advisories/GHSA-hxrm-9w7p-39cc
https://github.com/dotnet/aspnetcore/pull/24264

Hi @justinyoo  - Please take a peek at this PR, there's a high vulnerability that should be resolved for consumers of this library.

repo: Azure/azure-functions-openapi-extension


text:
Add template for Event Grid

https://github.com/Azure/azure-functions-templates/issues/646

https://github.com/Azure/azure-functions-templates/pull/703

Done.

authors: asavaritayal elprans

repo: Azure/azure-functions-python-worker


text:
Invoking a non-HTTP triggered function locally using the Azure Functions Core Tools Admin API (cardinality: many)

Is your question related to a specific version? If so, please specify:
Found Python version 3.8.5 (python3).
Azure Functions Core Tools (3.0.2931 Commit hash: d552c6741a37422684f0efab41d541ebad2b2bd2)
Function Runtime Version: 3.0.14492.0
What binding does your question apply to, if any? (e.g. Blob Trigger, Event Hub Binding, etc)
Event Hub Trigger Binding (cardinality: many)
Question
Hi there,
we are trying to follow the documentation about how to pass test data to a non-HTTP triggered function to invoke a Python function locally when running within the Azure Functions Core Tools host.
Within #764, @kepalas has been able to figure out how to invoke the function successfully when bound with cardinality: one - thank you so much! Within this issue, we would like to focus on cardinality: many instead.
With kind regards,
Andreas.

Hi there,
as a followup to #764, we are trying to figure out how to submit a list of events, reflected by a binding attribute "cardinality": "many" within function.json like that:
http http://0.0.0.0:7071/admin/functions/eventHubTrigger \
  input='{"SystemPropertiesArray":[{}],"data":[{"foo":"Ping from Az CLI IoT Extension #1","bar":{"id":"810d9efd-458c-49f2-a9c0-822c897a02e3","timestamp":"2020-10-28 23:24:16.315294"}}]}' \
  --print hHbB

The SystemPropertiesArray idea has been picked up from inspecting the source code of the tests within azure-functions-python-worker. However, I have no idea how to wrap the actual list of events. Using data here does not work yet.
According to EventHubConverter.decode(), one would have to somehow submit data of type collection_bytes or collection_string instead of string, bytes or json. Together with the grpc definition message TypedData, that might indicate that it is not possible to invoke a function binding to cardinality: many using plain JSON at all and instead it would only be possible using Protocol Buffers?
As far as we can see, one would have to supply the right input format to let the payload be funneled through EventHubTriggerConverter.decode_multiple_events() somehow, right?
While https://github.com/Azure/azure-functions-host/issues/3370 is not exactly about invoking the function locally, it shows at least that invoking a function which binds to some sort of collection (aka. cardinality: many) might not be as easy as for functions which bind to single events (aka. cardinality: one).
Maybe you are able to apply some additional wizardry from your pen, @kepalas?
With kind regards,
Andreas.

According to EventHubTriggerConverter.decode_multiple_events(), it should be possible to submit data of type json. However, data seems not to make it through to this method.
For investigating this further, we added the snippet
with open("/tmp/hello", "w") as f:
    f.write(str(trigger_metadata.keys()))

to the beginning of the EventHubTriggerConverter.decode() method.
The outcome for cardinality: one is:
dict_keys(['foo', 'Properties', 'SystemProperties', 'events', 'EnqueuedTimeUtc', 'bar', 'SequenceNumber'])

The outcome for cardinality: many is:
dict_keys(['Properties', 'SequenceNumber', 'events', 'EnqueuedTimeUtc'])

The consequence of this is that _is_cardinality_one() will work and return True, as SystemProperties is contained within the dictionary. However, in the case of cardinality: many, it will not work because _is_cardinality_many() will return False as SystemPropertiesArray is not contained within the dictionary.
I hope this helps for further getting more ideas what might be going on here.

Hi @amotl , Were you able to crack this issue ? We are also trying to send a batch of events using the admin api (and keys). But unfortunately the structure we receive in functions is not what we are expecting.

authors: amotl imshinto


text:
Skip paths resolution if in Integration Test CI

Description

Fixes E2E Integration Test https://azfunc.visualstudio.com/Azure Functions/_build/results?buildId=17962&view=logs&j=12f1170f-54f2-53f3-20dd-22fc7dff55f9&t=7dae026f-9e99-5d65-075e-3f7579577f94
This is due to the CI environment is not expect to use the default path.
Validation with latest 1.2.3 Python Worker in Core Tools (in virtual environment)

Validation with latest 1.2.3 Python Worker in Core Tools (without virtual environment)

/cc: @francisco-gamino

PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which has 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] If applicable, the PR references the bug/issue that it fixes in the description.
[ ] New Unit tests were added for the changes made and CI is passing.

Quality of Code and Contribution Guidelines

[x] I have read the contribution guidelines.

Thnx for finding the issue @Hazhzeng. :)

authors: Hazhzeng vrdmr


text:
Telemetry data schema

Type of issue

[ ] Bug
[ ] New feature
[ x] Improvement

Description
How can we specify a telemetry schema for an actual device? The simulation service has a spec for this but nothing for a real device.

Hi @kidproquo
The schema for telemetry message is just json data format. It has _unit property but not required to show on the telemetry chart in the UI.
This is the sample message and the data section is used to show points on telemetry chart.
{
    "id": "truck-02.0;1530639961103",
    "doc.schemaversion": 1,
    "doc.schema": "d2cmessage",
    "device.id": "truck-02.0",
    "device.msg.schema": "device-sensors;v1",
    "data.schema": "StreamingJobs",
    "device.msg.created": 1530639961103,
    "device.msg.received": 1530639961103,
    "data": {
        "latitude": 47.2557756983126,
        "longitude": -121.174945042825,
        "speed": 29.5333629637181,
        "speed_unit": "mph",
        "temperature": 49.2050887991744,
        "temperature_unit": "F"
    },
    "_rid": "YiRNAIyK4wABAAAAAAAAAA==",
    "_self": "dbs/YiRNAA==/colls/YiRNAIyK4wA=/docs/YiRNAIyK4wABAAAAAAAAAA==/",
    "_etag": "\"0100e807-0000-0000-0000-5b3bb7450000\"",
    "_attachments": "attachments/",
    "_ts": 1530640197
}

Are you not able to see the telemetry data from your physical device show up on chart in the UI?

Thanks @ppathan. What about the ASA service? Does it need to know this schema for analytics?

The ASA service is pass through to CosmosDB for telemetry messages and uses the same schema.

authors: kidproquo ppathan


text:
Changes for browser-based login

MobileServiceLogin.js changes how it passes parameters to Platform.login(). Instead of passing the startUri and the endUri, it now passes an object. Different login implementations use different properties from the object for their working.
CordovaPopup implementation has been changed not to use the InAppBrowser. Instead, it simply delegates the login work to config.login.loginWithOptions(). This method is implemented by the Cordova plugin using native (iOS / Android) implementations. Attempting to perform a login without this method will simply fail.

@dhei @danderson00

repo: Azure/azure-mobile-apps-js-client

license_source: bigquery


text:
Fixed a few minor accessibility fixes

Fixed a copy&pasted item name to be unique
Fixed a missing item name
Fixed an item name containing the control type name

/azp run

repo: Azure/azure-remote-rendering-asset-tool


text:
[Hub Generated] Review request for Microsoft.Maps to add version stable/2021-02-01

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
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.

April 2021

When you expect to publish swagger? Please provide date, or month to public if date is not available yet.

April 2021

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
[x] Updating API in 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.

/azp run unifiedPipeline

Just making sure that this PR is removing endpoints, is it expected?

his PR is removing endpoints, is it expected?

Yes, removing privateAtlas is expected, we are retiring the resourceType and it being replaced with "creators" type.

@jorgecotillo is there some action which I need to take here? This PR is addressing a bunch of PLR criteria which is on deadline, I see dotnet sdk build is failing but I'm not sure if that's caused from my PR.

@ArcturusZhang - is there any action which is required from the dotnet sdk build failure here for me?

@varunkumta as per your comments made changes, but now we have cross version breaking changes. Any recommendations what I can do here?

/azp run

@ArcturusZhang
Business Justification:
MAPS Creator is a PLR item that was recently onboarded. The GA is 5/21, but will use a new swagger API version containing the new SKUs. Once that swagger is merged we can kick off the GA work for Azure CLI, PowerShell and Terraform.
Creator is a resource moving from Preview to GA. It has not been part of a SDK release previously, so no customers SDK customers should be broken as a result of the change. The change removes an incorrect pattern and moves the RP to the ARM recommended best practice in preparation for the GA release. Can you please look and sign off?

For python, the breaking change is ok

Hi @stack111 I understand, but unfortunately I cannot sign off on the breaking changes issue - it can only be signed off by the breaking change review board. Could you please follow the guidance above to open a breaking change review request with your justification?

@ArcturusZhang - we have the breaking changes approved. Please continue forward.

@ArcturusZhang - sorry I accidently clicked the wrong button and closed the PR, I reopened but it added the CI python tag back. Please approve as soon as we can.

We could merge this once we revert the changes on package.lock @stach111

authors: ArcturusZhang jorgecotillo msyyc stack111

repo: Azure/azure-rest-api-specs


text:
[Draft] schemaregistry tsp

Data Plane API - Pull Request

API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.

Link to API Spec engagement record issue:

Is this review for (select one):

[ ] a private preview
[ ] a public preview
[ ] GA release

Change Scope
This section will help us focus on the specific parts of your API that are new or have been modified. Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.

Design Document:
Previous API Spec Doc:
Updated paths:

❔Got questions? Need additional info?? We are here to help!

 Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

💬 Teams Channel
💌 email

Click here for links to tools, specs, guidelines & other good stuff
Tooling

Open API validation tools were run on this PR. Go here to see how to fix errors
Spectral Linting
Open API Hub

Guidelines & Specifications

Azure REST API Guidelines
OpenAPI Style Guidelines
Azure Breaking Change Policy

Helpful Links

Azure DevTools Wiki

We also need to get CI passing on this PR. Looks like TypeSpec validation is pointing out that the tspconfig.yaml isnt extending the azure core linter ruleset. You can follow the instructions provided in CI to run this check locally and fix any issues it reports.

/azp run

Per the breaking changes check, the old paths we removed, this is due to the directory update being made in this PR. The paths exist in the updated swagger.
Likewise the removedparameters warning seems to be a false positive, the api version param, endpoint, schema version params exist on the apis.

authors: catalinaperalta qiaozha swathipil


text:
[Hub Generated] Review request for Microsoft.Batch to add version stable/2023-11-01.18.0

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
Data Plane API - Pull Request

Add Resource Tags support to Pool Creation
-- Added resourceTags property to PoolSpecification definition
-- Added resourceTags property to CloudPool definition

Add SecurityProfile support to Pool Creation
-- Added serviceArtifactReference property to VirtualMachineConfiguration definition
-- Added securityProfile property to VirtualMachineConfiguration definition

Add ServiceArtifactReference and OSDisk support to Pool Creation
-- Added standardssd_lrs value to StorageAccountType enum
-- Added caching property to NodePlacementPolicyType definition
-- Added managedDisk property to NodePlacementPolicyType definition
-- Added diskSizeGB property to NodePlacementPolicyType definition
-- Added writeAcceleratorEnabled property to NodePlacementPolicyType definition
-- Added scaleSetVmResourceID property to VirtualMachineInfo definition

API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.

Link to API Spec engagement record issue:

Is this review for (select one):

[ ] a private preview
[ ] a public preview
[x] GA release

Change Scope
This section will help us focus on the specific parts of your API that are new or have been modified. Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.

Design Document:
Previous API Spec Doc:
Updated paths:

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
Swagger-Suppression-Process
to get approval.
❔Got questions? Need additional info?? We are here to help!

 Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

💬 Teams Channel
💌 email

Click here for links to tools, specs, guidelines & other good stuff
Tooling

Open API validation tools were run on this PR. Go here to see how to fix errors
Spectral Linting
Open API Hub

Guidelines & Specifications

Azure REST API Guidelines
OpenAPI Style Guidelines
Azure Breaking Change Policy

Helpful Links

Azure DevTools Wiki

fix https://github.com/Azure/azure-rest-api-specs/issues/26902

This needs the approval of the API Stewardship board.

authors: tjprescott wiboris


text:
Suppress warning regarding long running operation

We have a legacy service put into place long before current ARM standards. The warning being emitted can be suppressed until the team owning the service does updates in the future to bring the service into compliance.
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.

@lmazuel Here's your PR.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-node

Automation for azure-libraries-for-java

Automation for azure-sdk-for-go

@alvadb I take the PR since I have email thread and context (I reviewed the previous one that implied this one). Thanks.

LGTM to me, thanks for the quick PR!

authors: AutorestCI d3r3kk lmazuel


text:
Alec baird desktopvirtualization microsoft.desktop virtualization 2024 01 16 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.

 Click here to see the details of Step 1
Breaking changes review (Diagram Step 1)
If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:

The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
You believe there is no need for you to request breaking change approval, for any reason.
Such claims must be reviewed, and the process is the same.

 Click here to see the details of Step 2
ARM API changes review (Diagram Step 2)

If this PR is in purview of ARM review then automation will add the ARMReview label.
If you want to force ARM review, add the label yourself.
Proceed according to the diagram at the top of this comment.

 Click here to see the diagram footnotes
Diagram footnotes
[1] ARM review queue (for merge queues, see [2])
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label ARMChangesRequested
is removed from your PR. This should cause the label WaitForARMFeedback to be added.
[2] public repo merge queue, private repo merge queue (for ARM review queue, [1])
If you need further help with anything, see Getting help section below.

Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

[x] New API version. (If API spec is not defined in TypeSpec, the PR should have been generated using OpenAPI Hub).
[ ] 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 swagger quality issues in S360.
[ ] 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
Swagger-Suppression-Process
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.
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.
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.

/pr RequestMerge


text:
Improve Salesforce V2 properties

Add "authenticationType" property in linked services
Change string type "readBehavior" to boolean type "includeDeletedObjects"

@lmazuel Could you help approve this PR?


text:
Add cognitiveservices\data-plane\LUIS\Authoring\readme.typescript.md

Auto generated

Can one of the admins verify this patch?

Automation for azure-sdk-for-python

Automation for azure-sdk-for-js

Automation for azure-sdk-for-node

Automation for azure-sdk-for-go

authors: AutorestCI azuresdkci kpajdzik


text:
[Hub Generated] Review request for Microsoft.Devices to add version preview/2019-03-22-preview

If you are a MSFT employee you can view your work branch via this link.
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.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-js

Automation for azure-sdk-for-java

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-go

Can one of the admins verify this patch?

closing this one will create a new one.

authors: AutorestCI azuresdkci reshantchandra


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

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

/check-enforcer reset

authors: azure-sdk sima-zhu

repo: Azure/azure-sdk-for-android


text:
Sample code for making a REST call

As far as I can tell, the documentation for this project is pretty awful. And I'm not the only one who stumbled across this: https://devblogs.microsoft.com/azure-sdk/cppintro/#comment-26
So, if you want to improve your product, I really suggest to add more samples and fix the documentation to not just go round in circles. Or, if such documentation already exists somewhere, make it easier to discover.
Anyway, I'd like to use the Azure Core SDK to do a simple REST call (using https), to replace my usage of cpprest with this library. However, I have no idea how to even start with that. Could someone post some sample code, how to do that?

We hear you on the documentation and are working to make that experience better.  If you have specific places that you ended up going in circles, please help point us to those places and we will work to remedy.
Azure::Core is not a direct replacement for cpprest.  Azure::Core is intended to be consumed by Azure client SDK libraries for communication with Azure.  Although it's possible to use it standalone to communicate with Azure, that is not an officially supported scenario.

Regarding the documentation, this is your main page:
https://azure.github.io/azure-sdk-for-cpp/
It explains the basics to get up and running, that is fine, but then you need a sample how to do this or that, but the page doesn't have that, so you go to the "Need help" section and there are two promising links. But the first link literally links to the same page and the second page links to something that doesn't seem to have any resources regarding this SDK. That's the point where I felt like somebody was making fun of me.
Regarding cpprest, on it's main page it says "cpprestsdk is in maintenance mode and we do not recommend its use in new projects. We will continue to fix critical bugs and address security issues."
That's it, it doesn't say what to use instead. So IS there anything else one could use? I thought that since the Azure SDKs do REST calls all the time, this would should be possible to use for me as well.

authors: RickWinter jankrassnigg

repo: Azure/azure-sdk-for-cpp


text:
override HTTP transport

Service Package Request
Is there a way to override HTTP transport of the get request?
	groupsBuilder := graphClient.UsersById(OID).MemberOf()
	params := &users.ItemMemberOfRequestBuilderGetRequestConfiguration{<mysettings>}
	// Get the group memberships of the user
	groupsIds, err := groupsBuilder.Get(ctx, params)
	if err != nil {
		return nil, err
	}

@jhendrixMSFT

solved it by using NewGraphRequestAdapterWithParseNodeFactoryAndSerializationWriterFactoryAndHttpClient

repo: Azure/azure-sdk-for-go


text:
Azure Firewall Application Rule Collection Mssql Support

Feature Request
According to the API documentation for Azure Firewall Application Rule Collections the supported protocol options are Http, Https, & Mssql ( https://docs.microsoft.com/en-us/rest/api/firewall/azurefirewalls/createorupdate#azurefirewallapplicationruleprotocoltype ) this however is not reflected in the API client and thus not reflected in the Terraform Provider.
The ask here is to add the Mssql constant into the models.go for Networking.
From what I can see the models are dynamically generated so it would be pointless for me to PR the const in however, I am happy to do so.

Okay, so it seems this is actually declared in the 2019-07-01 version of the models.go. As such, this can be closed I believe.


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

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

/check-enforcer override

authors: azure-sdk benbp