Azure / Azure/azure-cli

azure storage private end-point not accepting resource-id

Open
#18,079 3 comments 0 reactions 2 assignees Claimed by @msyyc View on GitHub
act-quality-productivity-squad feature-request Network
Dominant language
Python
Stars
4.6k
Forks
3.5k
Avg merge
3d 2h
Merged PRs (30d)
60

Description

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

**Describe the bug**

When trying to create a private endpoint for storaging, using the resourceid, I get an error saying that I need either subnet ID or --subnet name and --vnet-name.

Example:

az network private-endpoint create -g storage-dr -n pe-test --connection-name test --private-connection-resource-id "/subscriptions/xxxxxxxxxxx/resourceGroups/storage-dr/providers/Microsoft.Storage/storageAccounts/dapolina02prem02" --location "eastus2" --subnet /subscriptions/xxxxxxxxxx/resourceGroups/storage-dr/providers/Microsoft.Network/virtualNetworks/eastus2-vnet/default --group-id blob
incorrect usage: **( --subnet ID | --subnet NAME --vnet-name NAME)**

**To Reproduce**

Run the command above

**Expected behavior**

The command should work with a resource ID when the storage account and VNET are in different resource groups.

**Environment summary**

You already have the latest azure-cli version: 2.23.0
**Additional context**

--subnet NAME and --vnet-name NAME work, but only when the VNET and storage account are in the same resource group.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.