text:
API Management shape in new designer does not create correct reference to API

Describe the Bug with repro steps

Create API management shape in new designer and point out API
The api shape is created in the logic app designer, named "s112-accountingentryitem" in arm template below. But in code view it points to the wrong template.

"template": "/s112-accountingentryitem/AccountingEntryItemv2"
I dont know where it gets the above from? Cannot be found in APIM.

Create API management shape in old designer and point out API
The api shape is created in the logic app designer, named "AccountingEntryItemv2" in arm template below. In code view it now points to the correct template.

"template": "/mip/hrplus/s112_EmployeeInformation/v1/bulkapi/AccountingEntryItemv2"
API URL Suffix: /mip/hrplus/s112_EmployeeInformation
Version: v1/
Operation: bulkapi/AccountingEntryItemv2
What type of Logic App Is this happening in?
Consumption (Portal)
Which operating system are you using?
Windows
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
{
  "definition": {
    "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
    "contentVersion": "1.0.0.0",
    "triggers": {
      "When_a_HTTP_request_is_received": {
        "type": "Request",
        "kind": "Http"
      }
    },
    "actions": {
      "s112-accountingentryitem": {
        "type": "ApiManagement",
        "inputs": {
          "api": {
            "id": "/subscriptions/xxx/resourceGroups/apimanagement/providers/Microsoft.ApiManagement/service/MyApimInstance/apis/s112-accountingentryitem"
          },
          "method": "get",
          "pathTemplate": {
            "template": "/s112-accountingentryitem/AccountingEntryItemv2"
          }
        },
        "runAfter": {}
      },
      "AccountingEntryItemv2": {
        "type": "ApiManagement",
        "inputs": {
          "api": {
            "id": "/subscriptions/xxx/resourceGroups/apimanagement/providers/Microsoft.ApiManagement/service/MyApimInstance/apis/s112-hrplus_employeeinformation"
          },
          "method": "get",
          "pathTemplate": {
            "template": "/mip/hrplus/s112_EmployeeInformation/v1/bulkapi/AccountingEntryItemv2"
          }
        },
        "runAfter": {
          "s112-accountingentryitem": [
            "SUCCEEDED"
          ]
        }
      }
    },
    "outputs": {},
    "parameters": {
      "$connections": {
        "type": "Object",
        "defaultValue": {}
      }
    }
  },
  "parameters": {
    "$connections": {
      "value": {}
    }
  }
}

Screenshots or Videos
No response
Browser
Chrome
Additional context
No response

Hi @apropl I tried to reproduce your issue and was not seeing the same behavior, I'll need some more information to investigate this properly.
Specifically I would like to take a look at the swagger file and the operation id you are trying to add.
I would also like to see the serialized code for your apim operation from both old and new designer.
If you have tried to run the operation after saving in new-designer could you also include any sort of runtime failure you are seeing?
For the swagger file if you do not have it you can just take a network trace instead (instructions here: https://agreeable-beach-04ed7ce1e.5.azurestaticapps.net/tsg#collecting-console-errors)
If you don't want to upload any of that information here you can go ahead and just email it directly to me at rileyevans@microsoft.com


text:
not able to connect cosmos database through managed identity

Describe the Bug with repro steps
go to designer and add an action.
search cosmos database query operation.
the UI just provides the connection string to be filled out.
I have already added logic app's managed identity into the cosmos db. not sure is it working and how to work it for managed identity.
https://ms.portal.azure.com/#view/Microsoft_Azure_EMA/DesignerEditor.ReactView/id/%2fsubscriptions%2fe5874924-875c-48d4-874b-1d410e6514c5%2fresourceGroups%2fmediavalidation-ppe%2fproviders%2fMicrosoft.Web%2fsites%2fmvsteststatus%2fworkflows%2fmvsteststatusmonitor/location/East%20US/isReadOnly~/true/isMonitoringView~/true/runId/08584748190643678493686429590CU00
What type of Logic App Is this happening in?
Standard (Portal)
Which operating system are you using?
Windows
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
No response
Screenshots or Videos
No response
Browser
edge
Additional context
No response

Hi @hsiangtingyang, from what I can tell the only connection authorization available for the Cosmos DB connector is via connection string, MI is not supported as far as I'm aware

Are there any future plans to support it in Logic Apps?

source: gharchive/issue

repo: Azure/LogicAppsUX

license: MIT

license_type: permissive

license_source: github-api


text:
Added Public IP address Availability Zone and Standard SKU rules

PR Summary
Fix #958
Fix #979
Added the following rules:

Azure.PublicIP.AvailabilityZone
Azure.PublicIP.StandardSKU

for the following types:

Microsoft.Network/publicIPAddresses

PR Checklist

[x] PR has a meaningful title
[x] Summarized changes
[x] Change is not breaking
[x] This PR is ready to merge and is not Work in Progress
Rule changes

[x] Unit tests created/ updated
[x] Rule documentation created/ updated
[x] Link to a filed issue
[x] Change log has been updated with change under unreleased section

@BernieWhite Made some changes in regards to your feedback. Let me know if they look good to you.

@ArmaanMcleod One suggestion, but otherwise all good to merge.

All good @BernieWhite, thanks for the review and feedback 🙂.  Removed the 2021_12 baseline test.
Will merge once CI passes if thats ok with you.

source: gharchive/pull-request


text:
Front Door with Private Link

I'm trying to update the scenario to use Front Door in place of Application Gateway but having problems with the Front Door module. I've had to fix some of the Terraform scripts, for example, in https://github.com/Azure/aca-landing-zone-accelerator/blob/main/scenarios/aca-internal/terraform/modules/06-front-door/local.tf
containerAppsDefaultDomainArray   = split(var.containerAppsDefaultDomainName, ".")
containerAppsNameIdentifier       = local.containerAppsDefaultDomainArray[index(local.containerAppsDefaultDomainArray, var.location)]

should be:
containerAppsDefaultDomainArray   = split(".", var.containerAppsDefaultDomainName)
containerAppsNameIdentifier       = local.containerAppsDefaultDomainArray[index(local.containerAppsDefaultDomainArray, var.location)-1]

which makes me wonder if this module has been tested?
Anyway after fixing some of the scripts I'm having problems when creating the Private Link Service. Here's the Terraform output:
╷
│ Error: creating Private Link Service: (Name "pls-fd-sbox-lz-01" / Resource Group "rg-sbox-spoke-lz-01"): network.PrivateLinkServicesClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="PrivateLinkServiceCannotBeCreatedInSubnetThatHasNetworkPoliciesEnabled" Message="Private link service /subscriptions/***/resourceGroups/rg-sbox-spoke-lz-01/providers/Microsoft.Network/privateLinkServices/pls-fd-sbox-lz-01 cannot be created in a subnet /subscriptions/***/resourceGroups/rg-sbox-spoke-lz-01/providers/Microsoft.Network/virtualNetworks/vnet-sbox-spoke-01/subnets/snet-infra since it has private link service network policies enabled." Details=[]
│
│   with module.frontDoor.module.frontDoor.azurerm_private_link_service.privateLinkService,
│   on modules/frontdoor/main.tf line 6, in resource "azurerm_private_link_service" "privateLinkService":
│    6: resource "azurerm_private_link_service" "privateLinkService" ***
│
╵

I've looked around and I've found no complete solution for creating private ACA with Front Door through Private Link. The closest is https://github.com/microsoft/azure-container-apps/wiki/Create-a-private-ACA-environment-with-Azure-Front-Door
Do you have any guidance on this? Would love to get this working and happy to raise a PR for the fixes.

Just noticed https://github.com/microsoft/azure-container-apps/issues/867 and wondering if its worth continuing with Front Door if Private Link is unsupported with workload profile. Are there any other options for Front Door?

I'm struggling with the same thing: private linking to front door does not seem possible because the load balancer produced by Azure Container Apps is an IP-based load balancer (called capp-svc-lb) which is not supported by the Private Link Service. I've also added the same information on this issue: https://github.com/microsoft/azure-container-apps/issues/867

Hi all, you are correct. the current implementation of ACA with workload profiles, uses a load balancer with IP based Backend Pool which can’t function as a Private Link service. So for the time being AFD is not supported scenario. PG has flagged the related Issue in ACA repo as in progress/roadmap (https://github.com/orgs/microsoft/projects/540/views/1?query=is%3Aopen+sort%3Aupdated-desc&pane=issue&itemId=35488023).

authors: nad-au thotheod wsloth

repo: Azure/aca-landing-zone-accelerator


text:
Validate kubernetesConfig inside openshiftConfig

After an Openshift generate, the resulting apimodel has openshiftConfig.kubernetesConfig.networkPlugin and subsequently kubernetesConfig.networkPlugin set to kubenet which is a red herring and needs to be cleaned up. In general, we may want to rethink embedding kubernetesConfig...
@jim-minter @kwoodson @pweil-

So far I haven't seen any reason for having it. Unless we actually change this inside OpenShift (unlike), I am in favor of removing.

repo: Azure/acs-engine

license: mit

license_source: bigquery


text:
Add cluster-autoscaler addon documentation

What this PR does / why we need it:
It mentions cluster-autoscaler add-on in cluster definition documentation. The feature is present in acs-engine but it is not documented and because of it users are not able to use it.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
If applicable:

[x] documentation
[ ] unit tests
[ ] tested backward compatibility (ie. deploy with previous version, upgrade with this branch)

Release note:

/assign @jackfrancis

@sozercan Can you confirm that we will want to mention VMSS-only support for this addon?

@jackfrancis yes, it is VMSS only right now. It has a validation against availability sets if you try to generate/deploy.

The change lgtm.
cluster-autoscaler also works for vmas. @sozercan Would you like to also add vmas support? (in another PR)

@jackfrancis we should expand the addons docs to include the missing addons (nvidia-device-plugin, oms, aci-connector, etc.) - in a separate PR

authors: CecileRobertMichon diwakar-s-maurya feiskyer jackfrancis sozercan


text:
Document the required AAD Apps that require Kusto viewer permissions

It would be good to document the various ADX-Mon AAD Apps that require Kusto viewer permissions.
This is what I've captured from a couple of threads.
public cloud prod adx-mon app:
appID: c6a42369-7f08-4faf-a52f-d9c2f26863b3
tenantID: 33e01921-4d64-4f8c-a055-5bdaffd5e33d
public cloud prod deployment app used for CI:
appID: 785a3a96-8b24-4f18-8c50-f94400533fbd
tenantID: 33e01921-4d64-4f8c-a055-5bdaffd5e33d
publicintv2
appID: c8b9fc64-fc6a-471b-9a96-dae355f5fe2e
tenantID: 33e01921-4d64-4f8c-a055-5bdaffd5e33d
corpdev: 1e14d0ca-5439-4345-85c9-4bd1459294e5
tenant: 72f988bf-86f1-41af-91ab-2d7cd011db47
corptest: c0d69910-3ed9-4abd-8d5b-c186731c2dde
tenant: 72f988bf-86f1-41af-91ab-2d7cd011db47

This is specific to our deployment of this project internally and not to the OSS project.

repo: Azure/adx-mon


text:
Register new CRDs & Autogenerate CRD Clients

This PRs introduces the required Go code to register the new CRDS, based on which we generate the following https://github.com/Azure/application-gateway-kubernetes-ingress/pull/282
This is a small chunk from https://github.com/Azure/application-gateway-kubernetes-ingress/pull/267

@akshaysngupta  I struggled to find a decent way to make informers.HasSynced() == true in the WaitForCacheSync section for the CRDs during unit tests here: .  So for the time being I added a bool to bypass that while testing: https://github.com/Azure/application-gateway-kubernetes-ingress/pull/283/files#diff-f0d560b01cfd4dd3863dff1cb96b71edR256
I'm going to spend some time fixing this as soon as we ship this feature first.
PTAL


text:
Change the subscriptionId paremeter to be completely optional

The Azure Login action already sets your subscription id:
https://github.com/Azure/login/blob/master/src/main.ts#L39
This change makes usage a bit cleaner.

So sorry 😞, this went completely under the radar.
The change looks good to me. @pulkitaggarwl / @kanika1894 any comments? Pulkit, please look at this as well.

So sorry 😞, this went completely under the radar.
The change looks good to me. @pulkitaggarwl / @kanika1894 any comments? Pulkit, please look at this as well.

looks good to me.

So sorry 😞, this went completely under the radar.
The change looks good to me. @pulkitaggarwl / @kanika1894 any comments? Pulkit, please look at this as well.

looks good to me.

Looks good. Thanks @harvey-k  for the contribution

authors: bishal-pdMSFT harvey-k kanika1894 pulkitaggarwl

repo: Azure/arm-deploy


text:
Should we default to long for integer types?

Spec doesn't define that integer type is int32 .

Blocked by https://github.com/Azure/autorest.modelerfour/issues/288

From https://github.com/Azure/autorest.modelerfour/issues/288#issuecomment-649063965 -

I just read back over the initial conversation that @pakrym linked in the issue description. It sounds like there isn't anything actionable to do in AutoRest/Modelerfour at this moment, correct?

@johanste's proposal was mainly to add a linting rule (which @lmazuel filed a request for) and gradually get all service Swaggers to explicitly specify the format for each usage of integer. I got the impression that we want to hold off on making int64 the default for now since that might be an unexpected change for service teams (and SDK library users).

authors: ShivangiReja pakrym


text:
Make RequestMethodAdditional internal

Fixes https://github.com/Azure/autorest.csharp/pull/482

I'm a little confused why the Fixes link for this PR is to anther PR... copy/paste user error? :-P

Yep.
Fixes: https://github.com/Azure/autorest.csharp/issues/472

authors: MiYanni pakrym


text:
Fixed several issues related to SDK

For polling call, request body is not needed
Fixed a naming issue related to enum

/azp run


text:
read error response in try catch

fixes #2685

@iscai-msft overall looks good and I commit a little optimization to your PR.

authors: iscai-msft msyyc


text:
[New azd-template] Jupyter Notebooks Web App on Azure Container Apps

New azd-template Submission
Fill in the sections below to populate a new gallery card for your template. All fields are mandatory unless explicitly identified as optional
1. Description
1-2 sentence description of the architecture or solution that is defined by the template. If this is a requested template, please tag the GitHub issue containing the request.
A web application used for hosting, sharing, and interacting with Jupyter Notebooks via Mercury, hosted on Azure Container Apps.
2. Author Information
Name: Savannah Ostrowski
Link: https://github.com/savannahostrowski
3. Template Repo
The GitHub repo containing the template being contributed-- must be a valid, complete template
https://github.com/savannahostrowski/jupyter-mercury-aca
4. Link to PR where you made your repo azd compatible
To allow us to provide feedback on your template, please include a link to the PR where you added azd compatibility
There's no particular commit, unfortunately.
5. Tags
Standard: One or more tags representing the template. Look at the currently available tags on the Gallery page. Provide at least 1 tag for programming language used and at least 1 tag for Azure services integrated. Also tag the IaC provider (Bicep or Terraform)
Python, Web Apps, Azure Container Apps, Bicep
Additional: Don't see a relevant tag for your template? Suggest tags to be added and used for your template. These could be new languages, services, or application domains.
Jupyter, Data Science
6. Architecture Diagram or Application Screenshot
Used as display image for gallery card-- should include all services and their connections. Example
https://github.com/savannahostrowski/jupyter-mercury-aca/blob/main/demo.png
7. Related Issues (optional)
Is this a template that was requested in a separate issue? If so, please tag the related issue here.
N/A

Next Steps
Once submitted, the issue will be reviewed - we plan to do reviews on a rolling basis at regular intervals. The process will include verifying all information required for the template gallery is provided and the template works (i.e., successfully deploys to Azure with azd up).

If we have questions or enhancements, we will add comments in issue thread (issue stays open)
If the contribution is approved, we'll update the gallery directly (issue will then be closed)

@v-xuto can you do a dry-run on this template and update here for any issues/feedback?

@savannahostrowski  We have finished testing this template. We found an issue in README and filed the issue, please review and update. Issue link: https://github.com/savannahostrowski/jupyter-mercury-aca/issues/7

Addressed the above bug @v-xuto @rajeshkamal5050

@rajeshkamal5050 We've run this template without any issues.

@jongio kindly review it when you get a chance.
@hemarina please add it to gallery post review and approval by Jon.

I'd prefer app code to be in src or app folder, but not blocking.
:shipit:

authors: jongio rajeshkamal5050 savannahostrowski v-xuto

repo: Azure/awesome-azd


text:
SLURM : Uppercase queue name are not allowed

Version
1.0.33
Provisioning node will always failed in CC with error "Hostname not registered yes in DNS" => fix is to upgrade to CC for Slurm version 2.7.1

Note that https://github.com/Azure/az-hop/pull/1353 enforces lowercase queue names.
Please relax this constraint in the schema once the upgrade is applied

authors: ltalirz xpillons

repo: Azure/az-hop


text:
Update create_target.py to have lowercase target_storage_account_name

Update create_target.py to have lowercase target_storage_account_name

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

[ ] Have you run ./scripts/ci/test_static.sh locally? (pip install pylint flake8 required)
[ ] Have you run python scripts/ci/test_index.py -q locally?

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/VijayRod/azure-cli-extensions.git@patch-1#subdirectory=src/$EXT&egg=$EXT"

please rebase off of master, otherwise, looks good

authors: VijayRod azuresdkci williexu

repo: Azure/azure-cli-extensions


text:
Fix encoding of encryption key while setting to KeyVault.

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

[ ] Have you run ./scripts/ci/test_static.sh locally? (pip install pylint flake8 required)
[ ] Have you run python scripts/ci/test_index.py -q locally?

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/mayank88mahajan/azure-cli-extensions.git@vhd-enc-util#subdirectory=src/$EXT&egg=$EXT"


text:
Instructions do not work for default Visual Studio Code online Linux host

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
This a escalation from CLI GitHub docs repo
https://github.com/microsoftdocs/azure-docs-cli/issues/1649
Appears to be Ubuntu 18.04.1 (output of uname -a is "Linux 4f95409cc772 5.0.0-1023-azure #24~18.04.1-Ubuntu SMP Wed Oct 2 20:23:29 UTC 2019 x86_64 GNU/Linux.") Fails on "lsb_release -cs."
Help needed to understand if there is any ongoing issues which team is aware of , which might affect on what customer is trying to evaluate with Visual studio code online Linux host.
To Reproduce
Customer is following this documentation https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-apt?view=azure-cli-latest#feedback , but getting the following error
Expected behavior
The steps in the docs should work.
Environment summary
Ubuntu 18.04.1
Additional context
Please help evaluate any product related issues or its primarily doc needs to be updated

Thanks for reporting the issue. I will investigate.

I created a Ubuntu 18.04 vm and uname -a shows
Linux feng-ubuntu-18 5.0.0-1025-azure #27~18.04.1-Ubuntu SMP Mon Nov 11 15:19:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
I cannot reproduce the issue. lsb_release -cs gives me bionic as expected.

I have a similar issue,  lsb_release -cs gives me stretch (Debian?), even though uname -a says Ubuntu, and in fact when selecting the VM for my VSO environment, there were only Ubuntu options.

This environment is in EastUS, in case that's relevant.

@alexvy86 I set up a vsonline VM and can reproduce your result. azure-cli can be installed successfully.
This is more likely an issue with the VM system implementation for lsb_release and uname. There's a discrepancy here.

@alexvy86 any update? Can we close this issue?

Well, I didn't report the issue... I haven't checked if the VMs created by VS Online now behave correctly (lsb_release -cs and uname -a not contradicting each other) but I'd say maybe you can close this issue, since it doesn't have to do with Azure cli directly?

authors: BharathNimmala-MSFT alexvy86 fengzhou-msft yonzhan

repo: Azure/azure-cli


text:
az aks create error "allocated ports is not in an allowable range"

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
The load balancer outbound ports validation logic doesn't work correctly when specifying more than 1 outbound IP address in the Azure-CLI.
To Reproduce
az aks create --node-count 3 --load-balancer-managed-outbound-ip-count 2 --load-balancer-outbound-ports 42664

BadRequestError: Operation failed with status: 'Bad Request'. Details: Load balancer profile allocated ports is not in an allowable range given the number of nodes and IPs provisioned. Refer to https://aka.ms/aks/slb-ports for more details.

Expected behavior
This should succeed. 2 outbound IPs, 64000 ports each with three nodes should allow outbound ports per instance of 42664.
Environment summary
azure-cli                         2.17.1
core                              2.17.1
telemetry                          1.0.6
Extensions:
aks-preview                       0.4.71
Python location 'C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\Matt.azure\cliextensions'
Python (Windows) 3.6.8 (tags/v3.6.8:3c6b436a57, Dec 23 2018, 23:31:17) [MSC v.1916 32 bit (Intel)]
Legal docs and information: aka.ms/AzureCliLegal
Your CLI is up-to-date.
Windows
Major  Minor  Build  Revision

10     0      19042  0
Powershell
Version
5.1.19041.610
Additional context
I am able to set this value for the load balancer in the web portal.

aks

aks

authors: nettolicious yonzhan


text:
Live test regression

This issue is created by a program.
Latest testing results of Azure CLI
User Manual of Live Test Pipeline
Upgrading API Versions in Azure CLI Live Test Pipeline
Power BI Report
The below table shows modules that have regression. Code owners, please pay attention.

Module
Pass
Fail
Pass rate
Detail
Date
Time

acs
134
10
93.06%
Link
20210108
054003

acs
135
9
93.75%
Link
20210101
022128

advisor
5
2
71.43%
Link
20210108
054003

advisor
7
0
100.00%
Link
20210101
022128

ams
68
1
98.55%
Link
20210108
054003

ams
69
0
100.00%
Link
20210101
022128

appservice
242
3
98.78%
Link
20210108
054003

appservice
243
2
99.18%
Link
20210101
022128

batch
33
2
94.29%
Link
20210108
054003

batch
34
1
97.14%
Link
20210101
022128

configure
2
1
66.67%
Link
20210108
054003

configure
3
0
100.00%
Link
20210101
022128

resource
120
15
88.89%
Link
20210108
054003

resource
126
12
91.30%
Link
20210101
022128

sql
28
21
57.14%
Link
20210108
054003

sql
29
20
59.18%
Link
20210101
022128

storage
159
9
94.64%
Link
20210108
054003

storage
163
5
97.02%
Link
20210101
022128

Live test

Live test

@Juliehzl  for awareness.

@Juliehzl  for awareness.

@ThejaChoudary - Take a look at the failed tests from App Services

@ThejaChoudary - Take a look at the failed tests from App Services

@ankitkumarr / @fabiocav - Can one one of you look at the Function app test failure here .

@ankitkumarr / @fabiocav - Can one one of you look at the Function app test failure here .

@qwordy - az webapp up tests failures are expected. So please ignore this.
@panchagnula - FYI.

@qwordy - az webapp up tests failures are expected. So please ignore this.
@panchagnula - FYI.

@Kotasudhakarreddy Got it.

@Kotasudhakarreddy Got it.

authors: Kotasudhakarreddy qwordy yonzhan


text:
az bot directline create fails to set--enable-enhanced-auth

I know this is not about the docs itself, but I don't know where to submit an issue for an az bot command.
When using the following command:
az bot directline create --name myBot --resource-group myBot  --enable-enhanced-auth true --trusted-origins https://www.test1.com https://www.test2.com
The result is that the site is created but the isSecureSiteEnabled is false and the trustedOrigins are null:
"sites": [
{
"isBlockUserUploadEnabled": false,
"isEnabled": true,
"isSecureSiteEnabled": false,
"isV1Enabled": true,
"isV3Enabled": true,
"key": "xxxxx",
"key2": "xxxxx",
"siteId": "xxx",
"siteName": "Default",
"trustedOrigins": null
}
When running the exact same command for the second time, everything is set correctly;
"sites": [
{
"isBlockUserUploadEnabled": false,
"isEnabled": true,
"isSecureSiteEnabled": true,
"isV1Enabled": true,
"isV3Enabled": true,
"key": "xxxxx",
"key2": "xxxxx",
"siteId": "xxx",
"siteName": "Default Site",
"trustedOrigins": [
"https://www.test1.com",
"https://www.test2.com"
]
}
]
Basically it needs the command to run twice to get it right.

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

ID: 71bc2cda-94fc-b5dc-210c-35c04c79aa97
Version Independent ID: 42c469d4-88bb-4c44-d02b-b6e4c8efa7ba
Content: az bot directline
Content Source: latest/docs-ref-autogen/bot/directline.yml
Service: bot-service
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

bot

bot

Thanks for bringing this up @cxbuilders Im taking over the botservice component. I will asses and try to accommodate as soon as possible in the corresponding release.

Thanks for bringing this up @cxbuilders Im taking over the botservice component. I will asses and try to accommodate as soon as possible in the corresponding release.

@munozemilio Do you know if around yesterday something has changed in the Bot Channels regsitration resource setup. We are running now into the following issue: #6203

@cxbuilders Im not aware on any change. @swagatmishra2007 do you know what could be the reason>

i would need a botid to debug

@swagatmishra2007 as mentioned in the other issue this has resolved itself. The original issue is still there, takes two arm / azure cli runs to create a direct line channel where the securesiteenabled is actually coming through

that might be existing behavior ..i will bring it up for investigation and a possible fix

authors: cxbuilders munozemilio swagatmishra2007 yonzhan


text:
az login

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az account get-access-token
Errors:
Get Token request returned http error: 400 and server response: {"error":"invalid_grant","error_description":"AADSTS700082: The refresh token has expired due to inactivity. The token was issued on 2021-10-05T11:50:24.4394320Z and was inactive for 90.00:00:00.\r\nTrace ID: d580793e-e9a6-4b1e-8bcf-a868e4628700\r\nCorrelation ID: 37ed27a4-c7c0-46aa-82d5-78c1b329ef95\r\nTimestamp: 2022-07-04 10:28:43Z","error_codes":[700082],"timestamp":"2022-07-04 10:28:43Z","trace_id":"d580793e-e9a6-4b1e-8bcf-a868e4628700","correlation_id":"37ed27a4-c7c0-46aa-82d5-78c1b329ef95","error_uri":"https://login.microsoftonline.com/error?code=700082"}
Traceback (most recent call last):
Temp\pip-unpacked-wheel-rpp6y7vh\knack\cli.py, ln 215, in invoke
...

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az account get-access-token --output {} --resource {}

Expected Behavior
Environment Summary
Windows-10-10.0.18362-SP0
Python 3.6.8
Installer: MSI

azure-cli 2.17.1 *

Extensions:
azure-devops 0.18.0

Additional Context

@jiasli for awareness

The error message is pretty clear:

The refresh token has expired due to inactivity. The token was issued on 2021-10-05T11:50:24.4394320Z and was inactive for 90.00:00:00.

Please re-run az login.

authors: einkel jiasli yonzhan


text:
Azure CLI connect fail

Describe the bug
I'm encountering a connectivity issue when trying to run the following Azure CLI command
az storage blob list --container-name mycontainer --account-name mycvstorage --sas-token 'mytoken'
Related command
az storage blob list
Errors
<urllib3.connection.HTTPSConnection object at 0x000001EA965D9ED0>: Failed to establish a new connection: [Errno 11001] getaddrinfo failed
Issue script & Debug output
<urllib3.connection.HTTPSConnection object at 0x000001F0ECC07090>: Failed to establish a new connection: [Errno 11001] getaddrinfo failed
Expected behavior
list the container
Environment Summary
azure-cli                         2.55.0
core                              2.55.0
telemetry                          1.1.0
Dependencies:
msal                            1.24.0b2
azure-mgmt-resource             23.1.0b2
Python location 'C:\Program Files\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\liangcl01.azure\cliextensions'
Python (Windows) 3.11.5 (tags/v3.11.5:cce6ba9, Aug 24 2023, 14:38:34) [MSC v.1936 64 bit (AMD64)]
Legal docs and information: aka.ms/AzureCliLegal
Your CLI is up-to-date.
Additional context
No response

Thank you for opening this issue, we will look into it.

Hi @Clairelala do the other commands work like az storage account create and az storage container create?
Did you get the sas token through this command?
az storage container generate-sas --permissions rl --account-name satestbloblist --name container1 --start "2023-12-07T00:00:00Z" --expiry "2024-01-01T00:00:00Z" -o tsv
Another thing to try is run az login again.

authors: Clairelala calvinhzy yonzhan


text:
az network bastion ssh fails with "Missing required field: -n"

Describe the bug
The command to start ssh bastion fails with "Missing required field: -n" even if --name/-n is specified.
Related command
az network bastion ssh --name xxxx --resource-group xxxx --target-ip-address xx.xx.xx.xx --auth-type password --username vmadmin
Errors
InvalidArgumentValue: Missing required field: -n
Issue script & Debug output
cli.knack.cli: Command arguments: ['network', 'bastion', 'ssh', '--name', 'xxxxxx', '--resource-group', 'yyyyyyyyy', '--target-ip-address', 'xx.xx.xx.xx', '--auth-type', 'password', '--username', 'vmadmin', '--debug']
cli.knack.cli: __init__ debug log:
Enable color in terminal.
Enable VT mode.
cli.knack.cli: Event: Cli.PreExecute []
cli.knack.cli: Event: CommandParser.OnGlobalArgumentsCreate [<function CLILogging.on_global_arguments at 0x034BC988>, <function OutputProducer.on_global_arguments at 0x035E8A78>, <function CLIQuery.on_global_arguments at 0x03808848>]
cli.knack.cli: Event: CommandInvoker.OnPreCommandTableCreate []
cli.azure.cli.core: Modules found from index for 'network': ['azure.cli.command_modules.network', 'azure.cli.command_modules.privatedns', 'azext_bastion']
cli.azure.cli.core: Loading command modules:
cli.azure.cli.core: Name                  Load Time    Groups  Commands
cli.azure.cli.core: network                   1.764       117       459
cli.azure.cli.core: privatedns                0.049        14        60
cli.azure.cli.core: Total (2)                 1.813       131       519
cli.azure.cli.core: These extensions are not installed and will be skipped: ['azext_ai_examples', 'azext_next']
cli.azure.cli.core: Loading extensions:
cli.azure.cli.core: Name                  Load Time    Groups  Commands  Directory
cli.azure.cli.core: bastion                   0.031         2         9  C:\Users\firstname.name\.azure\cliextensions\bastion
cli.azure.cli.core: Total (1)                 0.031         2         9
cli.azure.cli.core: Loaded 131 groups, 528 commands.
cli.azure.cli.core: Found a match in the command table.
cli.azure.cli.core: Raw command  : network bastion ssh
cli.azure.cli.core: Command table: network bastion ssh
cli.knack.cli: Event: CommandInvoker.OnPreCommandTableTruncate [<function AzCliLogging.init_command_file_logging at 0x0401E3E8>]
cli.azure.cli.core.azlogging: metadata file logging enabled - writing logs to 'C:\Users\firstname.name\.azure\commands\2024-09-20.13-56-58.network_bastion_ssh.17752.log'.
az_command_data_logger: command args: network bastion ssh --name {} --resource-group {} --target-ip-address {} --auth-type {} --username {} --debug
cli.knack.cli: Event: CommandInvoker.OnPreArgumentLoad [<function register_global_subscription_argument.<locals>.add_subscription_parameter at 0x040443E8>]
cli.knack.cli: Event: CommandInvoker.OnPostArgumentLoad []
cli.knack.cli: Event: CommandInvoker.OnPostCommandTableCreate [<function register_ids_argument.<locals>.add_ids_arguments at 0x0405D988>, <function register_cache_arguments.<locals>.add_cache_arguments at 0x04073C08>, <function register_upcoming_breaking_change_info.<locals>.update_breaking_change_info at 0x04073C58>]
cli.knack.cli: Event: CommandInvoker.OnCommandTableLoaded []
cli.knack.cli: Event: CommandInvoker.OnPreParseArgs []
cli.knack.cli: Event: CommandInvoker.OnPostParseArgs [<function OutputProducer.handle_output_argument at 0x035E8AC8>, <function CLIQuery.handle_query_parameter at 0x03808898>, <function register_ids_argument.<locals>.parse_ids_arguments at 0x04073BB8>]
az_command_data_logger: extension name: bastion
az_command_data_logger: extension version: 1.2.0
cli.azure.cli.core.azclierror: Traceback (most recent call last):
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/aaz/_command_ctx.py", line 53, in format_args
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/aaz/_arg_fmt.py", line 415, in __call__
azure.cli.core.aaz.exceptions.AAZInvalidArgValueError: InvalidArgumentValue: Missing required field: -n

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 233, in invoke
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 666, in execute
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 733, in _run_jobs_serially
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 703, in _run_job
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 336, in __call__
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler
  File "C:\Users\firstname.name\.azure\cliextensions\bastion\azext_bastion\custom.py", line 146, in ssh_bastion_host
    bastion = Show(cli_ctx=cmd.cli_ctx)(command_args={
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/aaz/_command.py", line 155, in __call__
  File "C:\Users\firstname.name\.azure\cliextensions\bastion\azext_bastion\aaz\latest\network\bastion\_show.py", line 32, in _handler
    super()._handler(command_args)
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/aaz/_command.py", line 165, in _handler
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/aaz/_command_ctx.py", line 55, in format_args
azure.cli.core.azclierror.InvalidArgumentValueError: InvalidArgumentValue: Missing required field: -n

cli.azure.cli.core.azclierror: InvalidArgumentValue: Missing required field: -n
az_command_data_logger: InvalidArgumentValue: Missing required field: -n
cli.knack.cli: Event: Cli.PostExecute [<function AzCliLogging.deinit_cmd_metadata_logging at 0x0401E528>]
az_command_data_logger: exit code: 1
cli.__main__: Command ran in 2.848 seconds (init: 0.738, invoke: 2.110)
telemetry.main: Begin splitting cli events and extra events, total events: 1
telemetry.client: Accumulated 0 events. Flush the clients.
telemetry.main: Finish splitting cli events and extra events, cli events: 1
telemetry.save: Save telemetry record of length 3836 in cache file under C:\Users\firstname.name\.azure\telemetry\20240920135659369
telemetry.main: Begin creating telemetry upload process.
telemetry.process: Creating upload process: "C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\Lib\site-packages\azure\cli\telemetry\__init__.pyc C:\Users\firstname.name\.azure C:\Users\firstname.name\.azure\telemetry\20240920135659369"
telemetry.process: Return from creating process 21724
telemetry.main: Finish creating telemetry upload process.

Expected behavior
SSH connection to the target IP should be opened.
Environment Summary
PS C:\Users> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.3.5
PSEdition                      Core
GitCommitId                    7.3.5
OS                             Microsoft Windows 10.0.22621
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

PS C:\Users> az version
{
  "azure-cli": "2.64.0",
  "azure-cli-core": "2.64.0",
  "azure-cli-telemetry": "1.1.0",
  "extensions": {
    "bastion": "1.2.0",
    "ssh": "2.0.5"
  }
}

Additional context
No response

Thank you for opening this issue, we will look into it.

Same situation here. Unable to put in production now.
Do you have any ETA ?

Do you have any ETA ?
Not really. As a workaround, I use the bastion via browser. However, it would be more comfortable to use it via Powershell CLI also for tunneling... Thank you.

Same situation here. Maybe i can downgrade to a previous version like 2.53.0 where it was working 🤔

Downgrading the bastion extension to 1.1.1 fixes the issue for me
az extension remove -n bastion
az extension add --name bastion --version 1.1.1

The same problem with "az network bastion tunnel". Tested on MacOs and LInux.

@HeyangQin: Thanks for your hint. I have just downgraded the bastion extension and it works.

Piling on here, have the same error, @HeyangQin thanks for that tip, worked for me as well.

I was able to do this and get it working:
pip install azure-cli==2.53.0
This didn't work for me :(

Downgrading the bastion extension to 1.1.1 fixes the issue for me
az extension remove -n bastion
az extension add --name bastion --version 1.1.1

authors: HeyangQin ThatCheck kaymaylove labiol rolandstirnimann thecosmictrickster yonzhan


text:
Unable to update WebTest content in Availability test using Azure CLI

I have Availability test resource named "sla-live-myproject" which contains multistep web test. I want to configure CD using Azure DevOps to update this test on each change in code. I try to use Azure CLI task in release pipeline to do it.
Using az resource show I get details of this resource:
az resource show -g $ResoruceGroupName -n $ResourceName --resource-type Microsoft.Insights/webtests
I have received the next response
  "etag": "\"51016086-0000-0000-0000-5c29c1fd0000\"",
  "id": "/subscriptions/{guid}/resourceGroups/myproject-log/providers/microsoft.insights/webtests/sla-webapi-live-myproject",
  "identity": null,
  "kind": null,
  "location": "westeurope",
  "managedBy": null,
  "name": "sla-webapi-live-myproject",
  "plan": null,
  "properties": {
    "Configuration": {
      "WebTest": "**Xml with my test, uploaded manualy using portal**"
    },
    "Description": "Availability-api.webtest",
    "Enabled": true,
    "Frequency": 300,
    "Kind": "multistep",
    "Locations": [
      {
        "Id": "emea-nl-ams-azr"
      },
      {
        "Id": "emea-ru-msa-edge"
      },
      {
        "Id": "emea-se-sto-edge"
      },
      {
        "Id": "emea-gb-db3-azr"
      },
      {
        "Id": "emea-ch-zrh-edge"
      },
      {
        "Id": "emea-fr-pra-edge"
      }
    ],
    "Name": "sla-webapi",
    "RetryEnabled": true,
    "SyntheticMonitorId": "sla-webapi-live-myproject",
    "Timeout": 120,
    "provisioningState": "Succeeded"
  },
  "resourceGroup": "myproject-log",
  "sku": null,
  "tags": {
    "hidden-link:/subscriptions/guid/resourceGroups/myproject-log/providers/microsoft.insights/components/live-myproject": "Resource"
  },
  "type": "microsoft.insights/webtests"
}

Next I want to update property properties.Configuration.WebTest and set the updated XML test
az resource update -g $ResoruceGroupName -n $ResourceName --resource-type "microsoft.insights/webtests"  --set properties.Configuration.WebTest="<WebTest>{Content of web test}</WebTest>", but I got the next error
Operation failed with status: 'Bad Request'. Details: Bad Request.
What I do wrong? Is it my mistake or a possible bug in cli?
If it is my mistake, I think it can be good to make more informative response than simple "Bad Request" message.

You can run the command with --debug to see what is actually sent on the wire. It is possible that a special character is being interpreted by the shell and resulting in a broken input.

When I used this command with --debug parameter I also received the same response content with minimum information in it...
msrest.http_logger : {"code":"BadRequest","message":"Bad Request","innererror":{"diagnosticcontext":"bc8b32b6-0e7b-11e9-9d81-3497f63385af","time":"2019-01-02T10:47:06.5458729Z"}}
What about special characters escaping, I've tried to use the xml string returned by az resource show without any changes or with minimal changes ( changed url, etc) as well. az resource show  returns the xml with escaped special characters.

Bad Request is returned from the service, and using the generic resource update method, there is no way for the CLI to know what you are trying to do. It is almost certainly some kind of quoting or escaping issue with your input. If you are still having issues, please reopen.

authors: Relgon tjprescott


text:
Azure CLI from Azure functions

Hi,
I would like to run az cli from azure function powershell.
I will help me to use Azure functions with Azure cli to manage my Azure environment.
So far can't load Az modules,

@dariuszbz This is currently not supported. Is it possible to do it using Azure PowerShell?

I can use az cli from powershell and cmd.
I can't use azure rm from azure functions as well.
The only option I see is azure automation and azure rm + run as account.
On Mon, 13 May 2019, 17:59 Ahmed Elnably, notifications@github.com wrote:

@dariuszbz https://github.com/dariuszbz This is currently not
supported. Is it possible to do it using Azure PowerShell?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-cli/issues/9376?email_source=notifications&email_token=AEVINAUCVHZARJ75U5XEHQDPVGM6FA5CNFSM4HMPZJM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVI5YLQ#issuecomment-491904046,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEVINAXLUQQVUMPUHRBM2E3PVGM6FANCNFSM4HMPZJMQ
.

We announced the public preview of Azure Functions support for PowerShell, if the commands you want to use is also represented in Azure PowerShell, you can write a PowerShell function to run these commands
https://docs.microsoft.com/en-us/azure/azure-functions/functions-reference-powershell

Nor az cli, azure rm work.
What do you mean azure power shell? Is it azure rm module ? AZ CLI? What
are you referring to, please ?
On Mon, 13 May 2019, 21:58 Ahmed Elnably, notifications@github.com wrote:

We announced the public preview of Azure Functions support for PowerShell,
if the commands you want to use is also represented in Azure PowerShell,
you can write a PowerShell function to run these commands
https://docs.microsoft.com/en-us/azure/azure-functions/functions-reference-powershell
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-cli/issues/9376?email_source=notifications&email_token=AEVINAQWWK7EQMVBI6HFAEDPVHI7FA5CNFSM4HMPZJM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVJRJTI#issuecomment-491984077,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEVINASY7LQUNBON7J6WBXTPVHI7FANCNFSM4HMPZJMQ
.

It works from vscode (4ex Get-AzContext), but not from azure functions it
self.
On Mon, 13 May 2019 at 21:58, Ahmed Elnably notifications@github.com
wrote:

We announced the public preview of Azure Functions support for PowerShell,
if the commands you want to use is also represented in Azure PowerShell,
you can write a PowerShell function to run these commands
https://docs.microsoft.com/en-us/azure/azure-functions/functions-reference-powershell
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-cli/issues/9376?email_source=notifications&email_token=AEVINAQWWK7EQMVBI6HFAEDPVHI7FA5CNFSM4HMPZJM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVJRJTI#issuecomment-491984077,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEVINASY7LQUNBON7J6WBXTPVHI7FANCNFSM4HMPZJMQ
.

Ok I found:
first on your VM/workstation:
Connect-AzAccount
Save-AzContext
copy context json file to your azure function file system.
in your functions:
Import-AzContext -Path "D:\home\site\wwwroot\\azctx.json"
$az = Get-AzContext
write-host $az
works.
On Tue, 14 May 2019 at 11:20, Dariusz Bzówka daribzow@gmail.com wrote:

It works from vscode (4ex Get-AzContext), but not from azure functions it
self.
On Mon, 13 May 2019 at 21:58, Ahmed Elnably notifications@github.com
wrote:

We announced the public preview of Azure Functions support for
PowerShell, if the commands you want to use is also represented in Azure
PowerShell, you can write a PowerShell function to run these commands
https://docs.microsoft.com/en-us/azure/azure-functions/functions-reference-powershell
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-cli/issues/9376?email_source=notifications&email_token=AEVINAQWWK7EQMVBI6HFAEDPVHI7FA5CNFSM4HMPZJM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVJRJTI#issuecomment-491984077,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEVINASY7LQUNBON7J6WBXTPVHI7FANCNFSM4HMPZJMQ
.

Closed as resolved

authors: ahmedelnably dariuszbz


text:
[Network] Fix #23525: az network bastion create/update: Add missing arguments and update command

Related command

az network bastion create
az network bastion update

Description

Azure Bastion Hosts have a few configurations available from the Azure Portal but are missing in Azure CLI. This PR adds those configuration arguments and an update command as well.
resolves #23525, resolves #22595
Testing Guide

az network bastion create --name {} --resource-group {} --enable-native-client-support --disable-copy-paste --enable-ip-connect
az network bastion update --name {} --resource-group {} --enable-native-client-support --disable-copy-paste --enable-ip-connect

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.

Network

authors: PramodValavala-MSFT yonzhan


text:
{AKS} Fix monitoring addon related test cases

Related command

Description

Fix monitoring addon related test cases. The resource group for dcr has been changed from workspace rg to cluster rg by PR #23630.
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.

Queued a pipeline to verify the fix.


text:
[Network] az network vnet peering create: Mark --remote-vnet as required

Related command

Description

Resolve: https://github.com/Azure/azure-cli/issues/27193
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.

Network

authors: necusjz yonzhan


text:
update powershell script to configure workspace

Azure PowerShell team is removing Switch-AzureMode, which will be a breaking change to create a solid foundation for the future of Azure PowerShell. The changes are as follows and are targeted for release on Oct. 8th of 2015.
(as mentioned in https://github.com/Azure/azure-powershell/wiki/Deprecation-of-Switch-AzureMode-in-Azure-PowerShell)
Example script was modified to use new AzureRm* commands

@troyanov - Thanks for the updates. @ms-toddabel - Could you review and let me know if this has been addressed through some of your recent updates, or if the updates can be merged?

This article is no longer published.

Closed per author feedback.

authors: ms-toddabel troyanov tysonn

repo: Azure/azure-content


text:
No CPU information on the FeedIterator Diagnostics

{
	"name": "Typed FeedIterator ReadNextAsync",
	"id": "d3e94730-243a-4e1b-9a05-07943603df2a",
	"caller info": {
		"member": "OperationHelperWithRootTraceAsync",
		"file": "ClientContextCore.cs",
		"line": 244
	},
	"start time": "07:45:47:087",
	"duration in milliseconds": 5437.4239,
	"data": {
		"Client Configuration": {
			"Client Created Time Utc": "2021-11-17T16:15:13.5462590Z",
			"NumberOfClientsCreated": 1,
			"User Agent": "cosmos-netstandard-sdk/3.21.0|3.21.1|1|X64|Microsoft Windows 10.0.17763|.NET Core 3.1.16|S|",
			"ConnectionConfig": {
				"gw": "(cps:50, urto:5, p:False, httpf: False)",
				"rntbd": "(cto: 5, icto: -1, mrpc: 30, mcpe: 65535, erd: True, pr: ReuseUnicastPort)",
				"other": "(ed:False, be:False)"
			},
			"ConsistencyConfig": "(consistency: NotSet, prgns:[])"
		},
		"Operation Cancelled Exception": "System.OperationCanceledException: The operation was canceled.\r\n   at System.Threading.CancellationToken.ThrowOperationCanceledException()\r\n   at Microsoft.Azure.Documents.TimeoutHelper.ThrowGoneIfElapsed()\r\n   at Microsoft.Azure.Documents.StoreReader.ReadMultipleReplicasInternalAsync(DocumentServiceRequest entity, Boolean includePrimary, Int32 replicaCountToRead, Boolean requiresValidLsn, Boolean useSessionToken, ReadMode readMode, Boolean checkMinLSN, Boolean forceReadAll)\r\n   at Microsoft.Azure.Documents.StoreReader.ReadMultipleReplicaAsync(DocumentServiceRequest entity, Boolean includePrimary, Int32 replicaCountToRead, Boolean requiresValidLsn, Boolean useSessionToken, ReadMode readMode, Boolean checkMinLSN, Boolean forceReadAll)\r\n   at Microsoft.Azure.Documents.ConsistencyReader.ReadSessionAsync(DocumentServiceRequest entity, ReadMode readMode)\r\n   at Microsoft.Azure.Documents.BackoffRetryUtility`1.ExecuteRetryAsync(Func`1 callbackMethod, Func`3 callShouldRetry, Func`1 inBackoffAlternateCallbackMethod, TimeSpan minBackoffForInBackoffCallback, CancellationToken cancellationToken, Action`1 preRetryCallback)\r\n   at Microsoft.Azure.Documents.ShouldRetryResult.ThrowIfDoneTrying(ExceptionDispatchInfo capturedException)\r\n   at Microsoft.Azure.Documents.BackoffRetryUtility`1.ExecuteRetryAsync(Func`1 callbackMethod, Func`3 callShouldRetry, Func`1 inBackoffAlternateCallbackMethod, TimeSpan minBackoffForInBackoffCallback, CancellationToken cancellationToken, Action`1 preRetryCallback)\r\n   at Microsoft.Azure.Documents.ReplicatedResourceClient.<>c__DisplayClass30_0.<<InvokeAsync>b__0>d.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at Microsoft.Azure.Documents.RequestRetryUtility.ProcessRequestAsync[TRequest,IRetriableResponse](Func`1 executeAsync, Func`1 prepareRequest, IRequestRetryPolicy`2 policy, CancellationToken cancellationToken, Func`1 inBackoffAlternateCallbackMethod, Nullable`1 minBackoffForInBackoffCallback)\r\n   at Microsoft.Azure.Documents.ShouldRetryResult.ThrowIfDoneTrying(ExceptionDispatchInfo capturedException)\r\n   at Microsoft.Azure.Documents.RequestRetryUtility.ProcessRequestAsync[TRequest,IRetriableResponse](Func`1 executeAsync, Func`1 prepareRequest, IRequestRetryPolicy`2 policy, CancellationToken cancellationToken, Func`1 inBackoffAlternateCallbackMethod, Nullable`1 minBackoffForInBackoffCallback)\r\n   at Microsoft.Azure.Documents.StoreClient.ProcessMessageAsync(DocumentServiceRequest request, CancellationToken cancellationToken, IRetryPolicy retryPolicy, Func`2 prepareRequestAsyncDelegate)\r\n   at Microsoft.Azure.Cosmos.Handlers.TransportHandler.ProcessMessageAsync(RequestMessage request, CancellationToken cancellationToken)\r\n   at Microsoft.Azure.Cosmos.Handlers.TransportHandler.SendAsync(RequestMessage request, CancellationToken cancellationToken)\r\n   at Microsoft.Azure.Cosmos.Handlers.RouterHandler.SendAsync(RequestMessage request, CancellationToken cancellationToken)\r\n   at Microsoft.Azure.Cosmos.RequestHandler.SendAsync(RequestMessage request, CancellationToken cancellationToken)\r\n   at Microsoft.Azure.Cosmos.Handlers.AbstractRetryHandler.ExecuteHttpRequestAsync(Func`1 callbackMethod, Func`3 callShouldRetry, Func`3 callShouldRetryException, CancellationToken cancellationToken)\r\n   at Microsoft.Azure.Cosmos.Handlers.AbstractRetryHandler.SendAsync(RequestMessage request, CancellationToken cancellationToken)\r\n   at Microsoft.Azure.Cosmos.RequestHandler.SendAsync(RequestMessage request, CancellationToken cancellationToken)\r\n   at Microsoft.Azure.Cosmos.Handlers.DiagnosticsHandler.SendAsync(RequestMessage request, CancellationToken cancellationToken)\r\n   at Microsoft.Azure.Cosmos.RequestHandler.SendAsync(RequestMessage request, CancellationToken cancellationToken)\r\n   at Microsoft.Azure.Cosmos.Handlers.RequestInvokerHandler.SendAsync(RequestMessage request, CancellationToken cancellationToken)\r\n   at Microsoft.Azure.Cosmos.Handlers.RequestInvokerHandler.SendAsync(String resourceUriString, ResourceType resourceType, OperationType operationType, RequestOptions requestOptions, ContainerInternal cosmosContainerCore, FeedRange feedRange, Stream streamPayload, Action`1 requestEnricher, ITrace trace, CancellationToken cancellationToken)\r\n   at Microsoft.Azure.Cosmos.Pagination.NetworkAttachedDocumentContainer.MonadicReadFeedAsync(FeedRangeState`1 feedRangeState, ReadFeedPaginationOptions readFeedPaginationOptions, ITrace trace, CancellationToken cancellationToken)\r\n   at Microsoft.Azure.Cosmos.Pagination.PartitionRangePageAsyncEnumerator`2.MoveNextAsync(ITrace trace)\r\n   at Microsoft.Azure.Cosmos.Pagination.BufferedPartitionRangePageAsyncEnumerator`2.PrefetchAsync(ITrace trace, CancellationToken cancellationToken)\r\n   at Microsoft.Azure.Cosmos.Pagination.BufferedPartitionRangePageAsyncEnumerator`2.GetNextPageAsync(ITrace trace, CancellationToken cancellationToken)\r\n   at Microsoft.Azure.Cosmos.Pagination.PartitionRangePageAsyncEnumerator`2.MoveNextAsync(ITrace trace)\r\n   at Microsoft.Azure.Cosmos.Pagination.CrossPartitionRangePageAsyncEnumerator`2.MoveNextAsync(ITrace trace)\r\n   at Microsoft.Azure.Cosmos.ReadFeed.Pagination.CrossPartitionReadFeedAsyncEnumerator.MoveNextAsync(ITrace trace)\r\n   at Microsoft.Azure.Cosmos.ReadFeed.ReadFeedIteratorCore.ReadNextAsync(ITrace trace, CancellationToken cancellationToken)"
	},
	"children": [
		{
			"name": "MoveNextAsync",
			"id": "d00bf29d-7777-4ac6-b435-5d2fbea1488f",
			"caller info": {
				"member": "MoveNextAsync",
				"file": "CrossPartitionReadFeedAsyncEnumerator.cs",
				"line": 41
			},
			"start time": "07:45:47:087",
			"duration in milliseconds": 5437.2554,
			"children": [
				{
					"name": "MoveNextAsync",
					"id": "9ba18ed6-c197-422e-804d-7866912c988b",
					"caller info": {
						"member": "MoveNextAsync",
						"file": "CrossPartitionRangePageAsyncEnumerator.cs",
						"line": 113
					},
					"start time": "07:45:47:087",
					"duration in milliseconds": 5437.2228,
					"children": [
						{
							"name": "[\"cbbc8f9e59a1e1c99eb3b8780660627a\"] move next",
							"id": "89f03ac7-9685-4dcd-9a5d-5bde17c7c3a3",
							"caller info": {
								"member": "MoveNextAsync",
								"file": "PartitionRangePageAsyncEnumerator.cs",
								"line": 49
							},
							"start time": "07:45:47:087",
							"duration in milliseconds": 5437.1545,
							"children": [
								{
									"name": "Prefetch",
									"id": "9122f6f9-8582-4482-9ff7-aa694fa02cee",
									"caller info": {
										"member": "PrefetchAsync",
										"file": "BufferedPartitionRangePageAsyncEnumerator.cs",
										"line": 50
									},
									"start time": "07:45:47:087",
									"duration in milliseconds": 5437.0866,
									"children": [
										{
											"name": "[\"cbbc8f9e59a1e1c99eb3b8780660627a\"] move next",
											"id": "e7256f6d-dc61-40cd-a141-c97a6995efaa",
											"caller info": {
												"member": "MoveNextAsync",
												"file": "PartitionRangePageAsyncEnumerator.cs",
												"line": 49
											},
											"start time": "07:45:47:087",
											"duration in milliseconds": 5437.05,
											"children": [
												{
													"name": "Microsoft.Azure.Cosmos.Handlers.RequestInvokerHandler",
													"id": "040183e8-f02b-4d75-a5d6-0bad00da7ca4",
													"start time": "07:45:47:087",
													"duration in milliseconds": 5436.9772,
													"children": [
														{
															"name": "Microsoft.Azure.Cosmos.Handlers.DiagnosticsHandler",
															"id": "b9d3211e-8d6c-4cbe-bc2c-0c806986928c",
															"start time": "07:45:47:087",
															"duration in milliseconds": 5436.9044,
															"children": [
																{
																	"name": "Microsoft.Azure.Cosmos.Handlers.RetryHandler",
																	"id": "2cff06c9-ad4e-4f2c-8900-236b88a5414a",
																	"start time": "07:45:47:087",
																	"duration in milliseconds": 5436.8458,
																	"children": [
																		{
																			"name": "Microsoft.Azure.Cosmos.Handlers.RouterHandler",
																			"id": "ed730396-35ca-4424-b403-0949d8e1764f",
																			"start time": "07:45:47:087",
																			"duration in milliseconds": 5436.7665,
																			"children": [
																				{
																					"name": "Microsoft.Azure.Cosmos.Handlers.TransportHandler",
																					"id": "6326a8f0-7abc-4268-809e-320c1ea995fa",
																					"start time": "07:45:47:087",
																					"duration in milliseconds": 5436.7397,
																					"children": [
																						{
																							"name": "Microsoft.Azure.Documents.ServerStoreModel Transport Request",
																							"id": "5bc81083-9365-44d1-91e5-dedb6fb53ab2",
																							"caller info": {
																								"member": "ProcessMessageAsync",
																								"file": "TransportHandler.cs",
																								"line": 109
																							},
																							"start time": "07:45:47:087",
																							"duration in milliseconds": 5436.658,
																							"data": {
																								"Client Side Request Stats": {
																									"Id": "AggregatedClientSideRequestStatistics",
																									"ContactedReplicas": [],
																									"RegionsContacted": [
																										"https://registrar-cosmosdb-prod-westeurope.documents.azure.com/"
																									],
																									"FailedReplicas": [
																										"rntbd://cdb-ms-prod-westeurope1-fd72-az01.documents.azure.com:14320/apps/31ceca64-9f75-4dd7-b8a6-cb20525e5aea/services/bcdcccb9-bb3c-4199-899e-87a86e204afd/partitions/1e653fca-d1bf-4e61-8f19-a50d955602ef/replicas/132779869656822364s"
																									],
																									"AddressResolutionStatistics": [],
																									"StoreResponseStatistics": [
																										{
																											"ResponseTimeUTC": "2021-11-24T19:45:52.5239794Z",
																											"ResourceType": "Document",
																											"OperationType": "ReadFeed",
																											"LocationEndpoint": "https://registrar-cosmosdb-prod-westeurope.documents.azure.com/",
																											"StoreResult": {
																												"ActivityId": "310077f0-c6c3-4646-a685-8e016b7773e9",
																												"StatusCode": "Gone",
																												"SubStatusCode": "Unknown",
																												"LSN": -1,
																												"PartitionKeyRangeId": null,
																												"GlobalCommittedLSN": -1,
																												"ItemLSN": -1,
																												"UsingLocalLSN": true,
																												"QuorumAckedLSN": -1,
																												"SessionToken": null,
																												"CurrentWriteQuorum": -1,
																												"CurrentReplicaSetSize": -1,
																												"NumberOfReadRegions": -1,
																												"IsValid": false,
																												"StorePhysicalAddress": "rntbd://cdb-ms-prod-westeurope1-fd72-az01.documents.azure.com:14320/apps/31ceca64-9f75-4dd7-b8a6-cb20525e5aea/services/bcdcccb9-bb3c-4199-899e-87a86e204afd/partitions/1e653fca-d1bf-4e61-8f19-a50d955602ef/replicas/132779869656822364s",
																												"RequestCharge": 0,
																												"BELatencyInMs": null,
																												"transportRequestTimeline": {
																													"requestTimeline": [
																														{
																															"event": "Created",
																															"startTimeUtc": "2021-11-24T19:45:47.0874542Z",
																															"durationInMs": 0.0017
																														},
																														{
																															"event": "ChannelAcquisitionStarted",
																															"startTimeUtc": "2021-11-24T19:45:47.0874559Z",
																															"durationInMs": 0.0059
																														},
																														{
																															"event": "Pipelined",
																															"startTimeUtc": "2021-11-24T19:45:47.0874618Z",
																															"durationInMs": 0.0459
																														},
																														{
																															"event": "Transit Time",
																															"startTimeUtc": "2021-11-24T19:45:47.0875077Z",
																															"durationInMs": 5435.3744
																														},
																														{
																															"event": "Failed",
																															"startTimeUtc": "2021-11-24T19:45:52.5228821Z",
																															"durationInMs": 0
																														}
																													],
																													"requestSizeInBytes": 513
																												},
																												"TransportException": "A client transport error occurred: The request timed out while waiting for a server response. (Time: 2021-11-24T19:45:52.5230916Z, activity ID: 310077f0-c6c3-4646-a685-8e016b7773e9, error code: ReceiveTimeout [0x0010], base error: HRESULT 0x80131500, URI: rntbd://cdb-ms-prod-westeurope1-fd72-az01.documents.azure.com:14320/apps/31ceca64-9f75-4dd7-b8a6-cb20525e5aea/services/bcdcccb9-bb3c-4199-899e-87a86e204afd/partitions/1e653fca-d1bf-4e61-8f19-a50d955602ef/replicas/132779869656822364s, connection: 10.218.0.106:54418 -> 13.69.66.27:14320, payload sent: True)"
																											}
																										}
																									]
																								}
																							}
																						}
																					]
																				}
																			]
																		}
																	]
																}
															]
														}
													]
												}
											]
										}
									]
								}
							]
						}
					]
				}
			]
		}
	]
}

Fixed in version 3.22


text:
Fix maven test failing when not installed

Test_extractVersion was failing on my machine due to mvn installed. Add a mock for mvnw so that the test is happy.

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

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

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

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

MacOS -

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

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

MSI

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

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

Documentation

learn.microsoft.com documentation

title: Azure Developer CLI reference (preview)
description: This article explains the syntax and parameters for the various Azure Developer CLI Preview commands.
author: alexwolftmsft
ms.author: alexwolf
ms.date: 05/06/2023
ms.service: azure-dev-cli
ms.topic: conceptual
ms.custom: devx-track-azdevcli
Azure Developer CLI reference (preview)
This article explains the syntax and parameters for the various Azure Developer CLI Preview 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.
  -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 init: Initialize a new application.
azd monitor: Monitor a deployed application.
azd package: Packages the application's code to be deployed to Azure. (Beta)
azd pipeline: Manage and configure your deployment pipelines.
azd provision: Provision the Azure resources for an application.
azd restore: Restores the application's dependencies.
azd template: Find and view template details.
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
  -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.
      --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
  -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
  -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: Lists all configuration values.
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 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
  -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
Lists all configuration values.
Synopsis
Lists 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 list [flags]

Options
  -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 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
  -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
  -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
  -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 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
  -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
  -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
  -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
  -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.
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
  -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
  -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.
azd env new <environment> [flags]

Options
  -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 [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for 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
  -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
  -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 init
Initialize a new application.
azd init [flags]

Options
  -b, --branch string         The template branch to initialize from.
  -e, --environment string    The name of the environment to use.
  -h, --help                  Gets help for init.
  -l, --location string       Azure location for the new environment
      --subscription string   Name or ID of an Azure subscription to use for the new environment
  -t, --template string       The template to use when you initialize the project. 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.
azd monitor [flags]

Options
  -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                  Deploys all services that are listed in azure.yaml
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for package.

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.
Options
  -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: Create and configure your deployment pipeline by using GitHub or Azure Pipelines.
Back to top

azd pipeline config
Create and configure your deployment pipeline by using GitHub or Azure Pipelines.
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.
  -e, --environment string      The name of the environment to use.
  -h, --help                    Gets help for config.
      --principal-name string   The name of the service principal to use to grant access to Azure resources as part of the pipeline.
      --principal-role string   The role to assign to the service principal. (default "contributor")
      --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.
Back to top

azd provision
Provision the Azure resources for an application.
Synopsis
Provision the Azure resources for an application.
The command prompts you for the following values:

Environment name: The name of your environment.
Azure location: The Azure location where your resources will be deployed.
Azure subscription: The Azure subscription where your resources will be deployed.

Depending on what Azure resources are created, running this command might take a while. To view progress, go to the Azure portal and search for the resource group that contains your environment name.
azd provision [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for provision.

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.
azd restore <service> [flags]

Options
      --all                  Restores all services that are listed in azure.yaml
  -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 template
Find and view template details.
Options
  -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.
azd template show: Show details for a given template.
Back to top

azd template list
Show list of sample azd templates.
azd template list [flags]

Options
  -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: Find and view template details.
Back to top

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

Options
  -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.
Back to top

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

Options
  -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
  -h, --help   Gets help for version.

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

See also

Back to top

authors: azure-sdk weikanglim

repo: Azure/azure-dev


text:
Consider configured subscription in TokenCredential registration.

This change updates our registration of TokenCredential in our IoC container to consider the value of AZURE_SUBSCRIPTION_ID when it is set in the environment. When set, we now fetch the tenant that this subscription belongs to and use that as the default tenant for auth requests. This is required for subscriptions which are in a non default teant for the user.
Fixes: #3485

@weikanglim I read the discussion in https://github.com/Azure/azure-dev/issues/3485 and I think this fix is what you are getting at the problem was - we lost the ability to take the setting of AZURE_SUBSCRIPTION_ID into account and so we always make requests from the user's home tenant.
I added this back - I tried to make the logic robust against cases where either the *Environment didn't exist or it does but azd provision has not been run yet and so a subscription ID was not asigned.
I'm actually a bit worried about the container lifetime here - I'm not sure if Singleton is correct or we'd rather Scoped (I think that's likely more correct because *Lazy[*Environment] is itself scoped.  But it also feels like anything that consumes TokenCredential would also want to become scoped.
Maybe the right thing to do is to return a TokenCredential that holds on to the Lazy[Environment] and fetches this value each time we make a request instead of trying to do this up front the first time a credential is requested.  That would also support cases where the *Environment is created later or the subscription ID shows up later.

Maybe the right thing to do is to return a TokenCredential that holds on to the Lazy[Environment] and fetches this value each time we make a request instead of trying to do this up front the first time a credential is requested. That would also support cases where the *Environment is created later or the subscription ID shows up later.

Flushed this out in 86434dab936a5203fe55b70602bebd9edf532283 and also moved to the registration being scoped since the environment itself is scoped.