You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| **Business card model** | prebuilt-businessCard | Sample business card|`https://raw.githubusercontent.com/Azure-Samples/cognitive-services-REST-api-samples/de5e0d8982ab754823c54de47a47e8e499351523/curl/form-recognizer/rest-api/business_card.jpg`|
67
67
68
68
## POST request
69
69
@@ -168,4 +168,4 @@ Visit the Azure samples repository on GitHub to view the GET response for each o
168
168
|**Invoice model**|[Invoice model output](https://github.com/Azure-Samples/cognitive-services-quickstart-code/blob/master/rest/FormRecognizer/how-to-guide/invoice-model-output.json)|
169
169
|**Receipt model**|[Receipt model output](https://github.com/Azure-Samples/cognitive-services-quickstart-code/blob/master/rest/FormRecognizer/how-to-guide/receipt-model-output.json)|
170
170
|**ID document model**|[ID document model output](https://github.com/Azure-Samples/cognitive-services-quickstart-code/blob/master/rest/FormRecognizer/how-to-guide/id-document-model-output.json)|
171
-
|**Business card model**|[Business card model output](https://github.com/Azure-Samples/cognitive-services-quickstart-code/blob/master/rest/FormRecognizer/how-to-guide/business-card-model-output.json)|
171
+
|**Business card model**|[Business card model output](https://github.com/Azure-Samples/cognitive-services-quickstart-code/blob/master/rest/FormRecognizer/how-to-guide/business-card-model-output.json)|
> Remember to remove the key from your code when you're done, and never post it publicly. For production, use a secure way of storing and accessing your credentials like [Azure Key Vault](../../../../key-vault/general/overview.md). For more information, *see* Cognitive Services [security](../../../../cognitive-services/security-features.md).
Copy file name to clipboardExpand all lines: articles/azure-monitor/agents/azure-monitor-agent-data-collection-endpoint.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Define network settings and enable network isolation for Azure Moni
4
4
ms.topic: conceptual
5
5
author: shseth
6
6
ms.author: shseth
7
-
ms.date: 9/16/2022
7
+
ms.date: 10/14/2022
8
8
ms.custom: references_region
9
9
ms.reviewer: shseth
10
10
@@ -125,7 +125,8 @@ For your data collection endpoints, ensure the **Accept access from public netwo
125
125
126
126
:::image type="content" source="media/azure-monitor-agent-dce/data-collection-endpoint-network-isolation.png" lightbox="media/azure-monitor-agent-dce/data-collection-endpoint-network-isolation.png" alt-text="Screenshot that shows configuring data collection endpoint network isolation.":::
127
127
128
-
Associate the data collection endpoints to the target resources by editing the data collection rule in the Azure portal. On the **Resources** tab, select **Enable Data Collection Endpoints**. Select a DCE for each virtual machine. See [Configure data collection for Azure Monitor Agent](../agents/data-collection-rule-azure-monitor-agent.md).
128
+
### Associate DCEs to target machines
129
+
Associate the data collection endpoints to the target resources by editing the data collection rule in the Azure portal. On the **Resources** tab, select **Enable Data Collection Endpoints**. Select a DCE for each virtual machine. See [Configure data collection for Azure Monitor Agent](../agents/data-collection-rule-azure-monitor-agent.md).
129
130
130
131
:::image type="content" source="media/azure-monitor-agent-dce/data-collection-rule-virtual-machines-with-endpoint.png" lightbox="media/azure-monitor-agent-dce/data-collection-rule-virtual-machines-with-endpoint.png" alt-text="Screenshot that shows configuring data collection endpoints for an agent.":::
| Connectivity over Active/Active VPN gateways | Yes | No |
110
-
| Connectivity over Active/Active Zone Redundant gateways | Yes | Yes |
110
+
| Connectivity over Active/Active Zone Redundant gateways | No | No |
111
+
| Connectivity over Active/Passive Zone Redundant gateways | Yes | Yes |
111
112
| Connectivity over Virtual WAN (VWAN) | No | No |
112
113
113
114
\* This option will incur a charge on ingress and egress traffic that uses a virtual network peering connection. For more information, see [Virtual Network pricing](https://azure.microsoft.com/pricing/details/virtual-network/). For more general information, see [Virtual network peering](../virtual-network/virtual-network-peering-overview.md).
Copy file name to clipboardExpand all lines: articles/cosmos-db/analytical-store-introduction.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -402,6 +402,7 @@ Some points to consider:
402
402
* You can achieve longer retention of your operational data in the analytical store by setting ATTL >= TTTL at the container level.
403
403
* The analytical store can be made to mirror the transactional store by setting ATTL = TTTL.
404
404
* If you have ATTL bigger than TTTL, at some point in time you'll have data that only exists in analytical store. This data is read only.
405
+
* Currently we don't delete any data from analytical store. If you set your ATTL to any positive integer, the data won't be included in your queries and you won't be billed for it. But if you change ATTL back to `-1`, all the data will show up again, you will start to be billed for all the data volume.
Copy file name to clipboardExpand all lines: articles/healthcare-apis/iot/deploy-06-new-deploy.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: msjasteppe
5
5
ms.service: healthcare-apis
6
6
ms.subservice: fhir
7
7
ms.topic: quickstart
8
-
ms.date: 08/30/2022
8
+
ms.date: 10/14/2022
9
9
ms.author: jasteppe
10
10
---
11
11
@@ -77,7 +77,7 @@ For more information about authorizing access to Event Hubs resources, see [Auth
77
77
78
78
### Grant access to the FHIR service
79
79
80
-
The process for granting your MedTech service system-assigned managed identity access to your FHIR service requires the same 13 steps that you used to grant access to your device message event hub. There are two exceptions. The first is that, instead of navigating to the Access Control (IAM) menu from within your event hub (as outlined in steps 1-4), you should navigate to the equivalent Access Control (IAM) menu from within your FHIR service. The second exception is that, in step 6, your MedTech service system-assigned managed identity will require you to select the **View** button directly across from **FHIR Data Writer** access instead of the button across from **Azure Event Hubs Data Receiver**.
80
+
The process for granting your MedTech service system-assigned managed identity access to your **FHIR service** requires the same 13 steps that you used to grant access to your device message event hub. There are two exceptions. The first is that, instead of navigating to the **Access Control (IAM)** menu from within your event hub (as outlined in steps 1-4), you should navigate to the equivalent **Access Control (IAM)** menu from within your **FHIR service**. The second exception is that, in step 6, your MedTech service system-assigned managed identity will require you to select the **View** button directly across from **FHIR Data Writer** access instead of the button across from **Azure Event Hubs Data Receiver**.
81
81
82
82
The **FHIR Data Writer** role provides read and write access to your FHIR service, which your MedTech service uses to access or persist data. Because the MedTech service is deployed as a separate resource, the FHIR service will receive requests from the MedTech service. If the FHIR service doesn’t know who's making the request, it will deny the request as unauthorized.
| `--s` or `--IdScope` | True | The ID Scope of the DPS instance |
379
-
| `--i` or `--Id` | True | The registration ID when using individual enrollment, or the desired device ID when using group enrollment. The registration ID is a case-insensitive string (up to 128 characters long) of alphanumeric characters plus the special characters: `'-'`, `'.'`, `'_'`, `':'`. The last character must be alphanumeric or dash (`'-'`). The device ID must comply with the [Device ID string requirements](../iot-hub/iot-hub-devguide-identity-registry.md#device-identity-properties). |
380
-
| `--p` or `--PrimaryKey` | True | The primary key of the individual or group enrollment. |
381
-
| `--e` or `--EnrollmentType` | False | The type of enrollment: `Individual` or `Group`. Defaults to `Individual` |
378
+
| `--i` or `--IdScope` | True | The ID Scope of the DPS instance |
379
+
| `--r` or `--RegistrationId` | True | The registration ID is a case-insensitive string (up to 128 characters long) of alphanumeric characters plus the special characters: `'-'`, `'.'`, `'_'`, `':'`. The last character must be alphanumeric or dash (`'-'`). |
380
+
| `--p` or `--PrimaryKey` | True | The primary key of the individual enrollment or the derived device key of the group enrollment. See the [ComputeDerivedSymmetricKeySample](https://github.com/Azure/azure-iot-sdk-csharp/tree/main/provisioning/device/samples/Getting%20Started/ComputeDerivedSymmetricKeySample) for how to generate the derived key. |
382
381
| `--g` or `--GlobalDeviceEndpoint` | False | The global endpoint for devices to connect to. Defaults to `global.azure-devices-provisioning.net` |
383
382
| `--t` or `--TransportType` | False | The transport to use to communicate with the device provisioning instance. Defaults to `Mqtt`. Possible values include `Mqtt`, `Mqtt_WebSocket_Only`, `Mqtt_Tcp_Only`, `Amqp`, `Amqp_WebSocket_Only`, `Amqp_Tcp_only`, and `Http1`.|
384
383
@@ -391,13 +390,13 @@ To update and run the provisioning sample with your device information:
391
390
* Replace `<primarykey>` with the **Primary Key** that you copied from the device enrollment.
392
391
393
392
```cmd
394
-
dotnet run --s <id-scope> --i <registration-id> --p <primarykey>
393
+
dotnet run --i <id-scope> --r <registration-id> --p <primarykey>
395
394
```
396
395
397
396
7. You should now see something similar to the following output. A "TestMessage" string is sent to the hub as a test message.
398
397
399
398
```output
400
-
D:\azure-iot-sdk-csharp\provisioning\device\samples\How To\SymmetricKeySample>dotnet run --s 0ne00000A0A --i symm-key-csharp-device-01 --p sbDDeEzRuEuGKag+kQKV+T1QGakRtHpsERLP0yPjwR93TrpEgEh/Y07CXstfha6dhIPWvdD1nRxK5T0KGKA+nQ==
399
+
D:\azure-iot-sdk-csharp\provisioning\device\samples\How To\SymmetricKeySample>dotnet run --i 0ne00000A0A --r symm-key-csharp-device-01 --p sbDDeEzRuEuGKag+kQKV+T1QGakRtHpsERLP0yPjwR93TrpEgEh/Y07CXstfha6dhIPWvdD1nRxK5T0KGKA+nQ==
401
400
402
401
Initializing the device provisioning client...
403
402
Initialized for registration Id symm-key-csharp-device-01.
Copy file name to clipboardExpand all lines: includes/virtual-machines-disks-expand-without-downtime-restrictions.md
+24-3Lines changed: 24 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,16 +5,37 @@
5
5
author: roygara
6
6
ms.service: virtual-machines
7
7
ms.topic: include
8
-
ms.date: 08/23/2022
8
+
ms.date: 10/14/2022
9
9
ms.author: rogarana
10
10
ms.custom: include file
11
11
---
12
+
- Only available with particular VM SKUs.
12
13
- Only supported for data disks.
13
14
- If a disk is 4 TiB or less, you can't expand it beyond 4 TiB without deallocating the VM. If a disk is already greater than 4 TiB, you can expand it without deallocating the VM.
14
-
- Not supported for Ultra disks, Premium SSD v2 (preview) disks, or standard HDDs.
15
+
- Not supported for Ultra disks or Premium SSD v2 disks.
15
16
- Not supported for shared disks.
16
17
- Install and use either:
17
18
- The [latest Azure CLI](/cli/azure/install-azure-cli)
18
19
- The [latest Azure PowerShell module](/powershell/azure/install-az-ps)
19
20
- The [Azure portal](https://portal.azure.com/)
20
-
- Or an Azure Resource Manager template with an API version that's 2021-04-01 or newer.
21
+
- Or an Azure Resource Manager template with an API version that's `2021-04-01` or newer.
22
+
23
+
Use the following PowerShell script to determine which VM SKUs it's available with:
0 commit comments