Skip to content

Commit f0a86bd

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into privlnkvnetupd
commit
2 parents f3beb4a + 49c6a0e commit f0a86bd

21 files changed

+66
-57
lines changed

articles/active-directory/managed-identities-azure-resources/tutorial-linux-vm-access-cosmos-db.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -63,14 +63,14 @@ Next, add a data collection in the Cosmos DB account that you can query in later
6363

6464
## Retrieve the `principalID` of the Linux VM's system-assigned managed identity
6565

66-
To gain access to the Cosmos DB account access keys from the Resource Manager in the following section, you need to retrieve the `principalID` of the Linux VM's system-assigned managed identity. Be sure to replace the `<SUBSCRIPTION ID>`, `<RESOURCE GROUP>` (resource group in which you VM resides), and `<VM NAME>` parameter values with your own values.
66+
To gain access to the Cosmos DB account access keys from the Resource Manager in the following section, you need to retrieve the `principalID` of the Linux VM's system-assigned managed identity. Be sure to replace the `<SUBSCRIPTION ID>`, `<RESOURCE GROUP>` (resource group in which your VM resides), and `<VM NAME>` parameter values with your own values.
6767

6868
```azurecli-interactive
6969
az resource show --id /subscriptions/<SUBSCRIPTION ID>/resourceGroups/<RESOURCE GROUP>/providers/Microsoft.Compute/virtualMachines/<VM NAMe> --api-version 2017-12-01
7070
```
7171
The response includes the details of the system-assigned managed identity (note the principalID as it is used in the next section):
7272

73-
```bash
73+
```output
7474
{
7575
"id": "/subscriptions/<SUBSCRIPTION ID>/<RESOURCE GROUP>/providers/Microsoft.Compute/virtualMachines/<VM NAMe>",
7676
"identity": {
@@ -92,7 +92,7 @@ az role assignment create --assignee <MI PRINCIPALID> --role '<ROLE NAME>' --sco
9292

9393
The response includes the details for the role assignment created:
9494

95-
```
95+
```output
9696
{
9797
"id": "/subscriptions/<SUBSCRIPTION ID>/resourceGroups/<RESOURCE GROUP>/providers/Microsoft.DocumentDB/databaseAccounts/<COSMOS DB ACCOUNT>/providers/Microsoft.Authorization/roleAssignments/5b44e628-394e-4e7b-bbc3-d6cd4f28f15b",
9898
"name": "5b44e628-394e-4e7b-bbc3-d6cd4f28f15b",
@@ -155,13 +155,13 @@ The CURL response gives you the list of Keys. For example, if you get the read-
155155

156156
Now that you have the access key for the Cosmos DB account you can pass it to a Cosmos DB SDK and make calls to access the account. For a quick example, you can pass the access key to the Azure CLI. You can get the `<COSMOS DB CONNECTION URL>` from the **Overview** tab on the Cosmos DB account blade in the Azure portal. Replace the `<ACCESS KEY>` with the value you obtained above:
157157

158-
```bash
158+
```azurecli
159159
az cosmosdb collection show -c <COLLECTION ID> -d <DATABASE ID> --url-connection "<COSMOS DB CONNECTION URL>" --key <ACCESS KEY>
160160
```
161161

162162
This CLI command returns details about the collection:
163163

164-
```bash
164+
```output
165165
{
166166
"collection": {
167167
"_conflicts": "conflicts/",

articles/active-directory/managed-identities-azure-resources/tutorial-windows-vm-access-cosmos-db.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -123,13 +123,13 @@ The response give you the list of Keys. For example, if you get read-only keys:
123123
```
124124
Now that you have the access key for the Cosmos DB account you can pass it to a Cosmos DB SDK and make calls to access the account. For a quick example, you can pass the access key to the Azure CLI. You can get the `<COSMOS DB CONNECTION URL>` from the **Overview** tab on the Cosmos DB account blade in the Azure portal. Replace the `<ACCESS KEY>` with the value you obtained above:
125125

126-
```bash
126+
```azurecli
127127
az cosmosdb collection show -c <COLLECTION ID> -d <DATABASE ID> --url-connection "<COSMOS DB CONNECTION URL>" --key <ACCESS KEY>
128128
```
129129

130130
This CLI command returns details about the collection:
131131

132-
```bash
132+
```output
133133
{
134134
"collection": {
135135
"_conflicts": "conflicts/",

articles/app-service/app-service-web-get-started-html.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,9 @@ In the following example, replace <app_name> with a unique app name.
4545

4646
```bash
4747
cd html-docs-hello-world
48+
```
4849

50+
```azurecli
4951
az webapp up --location westeurope --name <app_name> --html
5052
```
5153

@@ -97,7 +99,7 @@ Save your changes and exit nano. Use the command `^O` to save and `^X` to exit.
9799

98100
You'll now redeploy the app with the same `az webapp up` command.
99101

100-
```bash
102+
```azurecli
101103
az webapp up --location westeurope --name <app_name> --html
102104
```
103105

@@ -125,7 +127,7 @@ The left menu provides different pages for configuring your app.
125127

126128
In the preceding steps, you created Azure resources in a resource group. If you don't expect to need these resources in the future, delete the resource group by running the following command in the Cloud Shell. Remember that the resource group name was automatically generated for you in the [create a web app](#create-a-web-app) step.
127129

128-
```bash
130+
```azurecli
129131
az group delete --name appsvc_rg_Windows_westeurope
130132
```
131133

articles/application-gateway/application-gateway-create-url-route-cli.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -214,7 +214,7 @@ done
214214

215215
To get the public IP address of the application gateway, you can use [az network public-ip show](/cli/azure/network/public-ip). Copy the public IP address, and then paste it into the address bar of your browser. Such as, `http://40.121.222.19`, `http://40.121.222.19:8080/images/test.htm`, or `http://40.121.222.19:8080/video/test.htm`.
216216

217-
```azurepowershell-interactive
217+
```azurecli-interactive
218218
az network public-ip show \
219219
--resource-group myResourceGroupAG \
220220
--name myAGPublicIPAddress \

articles/application-gateway/redirect-http-to-https-cli.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -33,13 +33,13 @@ If you choose to install and use the CLI locally, this quickstart requires that
3333

3434
For production use, you should import a valid certificate signed by a trusted provider. For this tutorial, you create a self-signed certificate and pfx file using the openssl command.
3535

36-
```azurecli-interactive
36+
```console
3737
openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout privateKey.key -out appgwcert.crt
3838
```
3939

4040
Enter values that make sense for your certificate. You can accept the default values.
4141

42-
```azurecli-interactive
42+
```console
4343
openssl pkcs12 -export -out appgwcert.pfx -inkey privateKey.key -in appgwcert.crt
4444
```
4545

@@ -203,7 +203,7 @@ az vmss extension set \
203203

204204
To get the public IP address of the application gateway, you can use [az network public-ip show](/cli/azure/network/public-ip). Copy the public IP address, and then paste it into the address bar of your browser.
205205

206-
```azurepowershell-interactive
206+
```azurecli-interactive
207207
az network public-ip show \
208208
--resource-group myResourceGroupAG \
209209
--name myAGPublicIPAddress \

articles/application-gateway/tutorial-ssl-cli.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,13 +34,13 @@ If you choose to install and use the CLI locally, this article requires you to r
3434

3535
For production use, you should import a valid certificate signed by trusted provider. For this article, you create a self-signed certificate and pfx file using the openssl command.
3636

37-
```azurecli-interactive
37+
```console
3838
openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout privateKey.key -out appgwcert.crt
3939
```
4040

4141
Enter values that make sense for your certificate. You can accept the default values.
4242

43-
```azurecli-interactive
43+
```console
4444
openssl pkcs12 -export -out appgwcert.pfx -inkey privateKey.key -in appgwcert.crt
4545
```
4646

articles/azure-functions/durable/durable-functions-event-publishing.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -31,29 +31,29 @@ Create an Event Grid topic for sending events from Durable Functions. The follow
3131

3232
Create a resource group with the `az group create` command. Currently, Azure Event Grid doesn't support all regions. For information about which regions are supported, see the [Azure Event Grid overview](../../event-grid/overview.md).
3333

34-
```bash
34+
```azurecli
3535
az group create --name eventResourceGroup --location westus2
3636
```
3737

3838
### Create a custom topic
3939

4040
An Event Grid topic provides a user-defined endpoint that you post your event to. Replace `<topic_name>` with a unique name for your topic. The topic name must be unique because it becomes a DNS entry.
4141

42-
```bash
42+
```azurecli
4343
az eventgrid topic create --name <topic_name> -l westus2 -g eventResourceGroup
4444
```
4545

4646
## Get the endpoint and key
4747

4848
Get the endpoint of the topic. Replace `<topic_name>` with the name you chose.
4949

50-
```bash
50+
```azurecli
5151
az eventgrid topic show --name <topic_name> -g eventResourceGroup --query "endpoint" --output tsv
5252
```
5353

5454
Get the topic key. Replace `<topic_name>` with the name you chose.
5555

56-
```bash
56+
```azurecli
5757
az eventgrid topic key list --name <topic_name> -g eventResourceGroup --query "key1" --output tsv
5858
```
5959

articles/azure-government/documentation-government-impact-level-5.md

Lines changed: 13 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -190,6 +190,16 @@ Azure Web Apps can be used in Azure Government supporting Impact Level 5 workloa
190190

191191
## Integration services
192192

193+
<a name="logic-apps"></a>
194+
195+
### [Azure Logic Apps](https://azure.microsoft.com/services/logic-apps/)
196+
197+
Azure Logic Apps can be used in Azure Government supporting all impact levels with no additional configuration in the following regions:
198+
199+
| **Service** | **USGov VA** | **USGov IA** | **USGov TX** | **USGov AZ** | **USDoD East** | **USDoD Cent** |
200+
| --- | --- | --- | --- | --- | --- | --- |
201+
| **Azure Logic Apps** | X | | X | X | | |
202+
193203
### [Azure Service Bus](https://azure.microsoft.com/services/service-bus/)
194204

195205
Azure Service Bus can be used in Azure Government supporting Impact Level 5 workloads in the following regions:
@@ -227,13 +237,9 @@ Azure Monitor can be used in Azure Government supporting all impact levels with
227237
| --- | --- | --- | --- | --- | --- | --- |
228238
| **Azure Monitor** | X | X | X | X | X | X |
229239

230-
### [Azure Scheduler](https://azure.microsoft.com/services/scheduler/)
231-
232-
Azure Scheduler can be used in Azure Government supporting all impact levels with no additional configuration in the following regions:
240+
### Azure Scheduler
233241

234-
| **Service** | **USGov VA** | **USGov IA** | **USGov TX** | **USGov AZ** | **USDoD East** | **USDoD Cent** |
235-
| --- | --- | --- | --- | --- | --- | --- |
236-
| **Azure Scheduler** | X | X | X | X | X | X |
242+
Azure Scheduler is being retired and replaced by [Azure Logic Apps](#logic-apps). To continue working with the jobs that you set up in Scheduler, please migrate to Azure Logic Apps as soon as possible by following this article, [Migrate Azure Scheduler jobs to Azure Logic Apps](https://docs.microsoft.com/scheduler/migrate-from-scheduler-to-logic-apps).
237243

238244
## Media services
239245

@@ -408,4 +414,4 @@ Azure SQL Stretch Database can be used in Azure Government supporting Impact Lev
408414

409415
| **Service** | **USGov VA** | **USGov IA** | **USGov TX** | **USGov AZ** | **USDoD East** | **USDoD Cent** |
410416
| --- | --- | --- | --- | --- | --- | --- |
411-
| **Azure SQL Stretch DB** | X | X | X | X | X | X |
417+
| **Azure SQL Stretch DB** | X | X | X | X | X | X |

articles/azure-resource-manager/templates/template-tutorial-create-linked-templates.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ To complete this article, you need:
3737
* Visual Studio Code with Resource Manager Tools extension. See [Use Visual Studio Code to create Azure Resource Manager templates](use-vs-code-to-create-template.md).
3838
* To increase security, use a generated password for the virtual machine administrator account. Here is a sample for generating a password:
3939

40-
```azurecli-interactive
40+
```console
4141
openssl rand -base64 32
4242
```
4343

articles/azure-resource-manager/templates/template-tutorial-create-templates-with-dependent-resources.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ To complete this article, you need:
3131
* Visual Studio Code with Resource Manager Tools extension. See [Use Visual Studio Code to create Azure Resource Manager templates](use-vs-code-to-create-template.md).
3232
* To increase security, use a generated password for the virtual machine administrator account. Here is a sample for generating a password:
3333

34-
```azurecli-interactive
34+
```console
3535
openssl rand -base64 32
3636
```
3737
Azure Key Vault is designed to safeguard cryptographic keys and other secrets. For more information, see [Tutorial: Integrate Azure Key Vault in Resource Manager Template deployment](./template-tutorial-use-key-vault.md). We also recommend you to update your password every three months.

0 commit comments

Comments
 (0)