Skip to content

Commit 571fdd4

Browse files
authored
Merge pull request #202319 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
2 parents 907eb0f + 6c2ab3b commit 571fdd4

File tree

4 files changed

+23
-11
lines changed

4 files changed

+23
-11
lines changed

articles/azure-sql-edge/deploy-onnx.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -180,6 +180,9 @@ onnx_model_path = 'boston1.model.onnx'
180180
onnxmltools.utils.save_model(onnx_model, onnx_model_path)
181181
```
182182

183+
> [!NOTE]
184+
> You may need to set the `target_opset` parameter for the skl2onnx.convert_sklearn function if there is a mismatch between ONNX runtime version in SQL Edge and skl2onnx packge. For more information, see the [SQL Edge Release notes](release-notes.md) to get the ONNX runtime version corresponding for the release, and pick the `target_opset` for the ONNX runtime based on the [ONNX backward compatibility matrix](https://github.com/microsoft/onnxruntime/blob/master/docs/Versioning.md#version-matrix).
185+
183186
## Test the ONNX model
184187

185188
After converting the model to ONNX format, score the model to show little to no degradation in performance.

articles/azure-sql-edge/release-notes.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,12 +9,20 @@ ms.subservice:
99
author: kendalvandyke
1010
ms.author: kendalv
1111
ms.reviewer: jroth
12-
ms.date: 11/24/2020
12+
ms.date: 6/21/2022
1313
---
1414
# Azure SQL Edge release notes
1515

1616
This article describes what's new and what has changed with every new build of Azure SQL Edge.
1717

18+
## Azure SQL Edge 1.0.6
19+
20+
SQL engine build 15.0.2000.1565
21+
22+
### What's new?
23+
24+
- Security bug fixes
25+
1826
## Azure SQL Edge 1.0.5
1927

2028
SQL engine build 15.0.2000.1562

articles/virtual-machines/windows/tutorial-config-management.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -69,8 +69,8 @@ For pricing information, see [Automation pricing for Update management](https://
6969
To enable Update Management for your VM:
7070

7171
1. Navigate to your VM in the Azure portal (search for **Virtual machines** in the search bar, then choose a VM from the list).
72-
1. Select **Guest + host updates** under Operations.
73-
1. Click on **Go to Update management**.
72+
1. Select **Updates** under Operations.
73+
1. Click on **Go to Updates using automation**.
7474
1. The **Enable Update Management** window opens.
7575

7676
Validation is done to determine if Update Management is enabled for this VM. Validation includes checks for a Log Analytics workspace, for a linked Automation account, and for whether the solution is in the workspace.

includes/azure-monitor-limits-workspaces.md

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -13,20 +13,21 @@ ms.custom: "include file"
1313

1414
**Data collection volume and retention**
1515

16-
| Tier | Limit per day | Data retention | Comment |
16+
| Pricing tier | Limit per day | Data retention | Comment |
1717
|:---|:---|:---|:---|
18-
| Current Per GB pricing tier<br>(introduced April 2018) | No limit | 30 - 730 days | Data retention beyond 31 days is available for additional charges. Learn more about [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor). |
19-
| Legacy Free tiers<br>(introduced April 2016) | 500 MB | 7 days | When your workspace reaches the 500 MB per day limit, data ingestion stops and resumes at the start of the next day. A day is based on UTC. Data collected by Microsoft Defender for Cloud isn't included in this 500 MB per day limit and will continue to be collected above this limit. |
20-
| Legacy Standalone Per GB tier<br>(introduced April 2016) | No limit | 30 to 730 days | Data retention beyond 31 days is available for additional charges. Learn more about [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor). |
21-
| Legacy Per Node (OMS)<br>(introduced April 2016) | No limit | 30 to 730 days | Data retention beyond 31 days is available for additional charges. Learn more about [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor). |
22-
| Legacy Standard tier | No limit | 30 days | Retention can't be adjusted |
23-
| Legacy Premium tier | No limit | 365 days | Retention can't be adjusted |
18+
| [Pay-as-you-go](https://docs.microsoft.com/azure/azure-monitor/logs/cost-logs#pricing-model)<br>(introduced April 2018) | No limit | up to 730 days interactive retention /<br> up to 7 years [data archive](https://docs.microsoft.com/azure/azure-monitor/logs/data-retention-archive) | Data retention beyond 31 days is available for additional charges. Learn more about [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor). |
19+
| [Commitment tiers](https://docs.microsoft.com/azure/azure-monitor/logs/cost-logs#commitment-tiers)<br>(introduced November 2019) | No limit | up to 730 days interactive retention /<br> up to 7 years [data archive](https://docs.microsoft.com/azure/azure-monitor/logs/data-retention-archive) | Data retention beyond 31 days is available for additional charges. Learn more about [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor). |
20+
| [Legacy Per Node (OMS)](https://docs.microsoft.com/azure/azure-monitor/logs/cost-logs#per-node-pricing-tier)<br>(introduced April 2016) | No limit | 30 to 730 days | Data retention beyond 31 days is available for additional charges. Learn more about [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor). Access to use tier is limited to subscriptions that contained a Log Analytics workspace or Application Insights resource on April 2, 2018, or are linked to an Enterprise Agreement that started before February 1, 2019 and is still active. |
21+
| [Legacy Standalone tier](https://docs.microsoft.com/azure/azure-monitor/logs/cost-logs#standalone-pricing-tier)<br>(introduced April 2016) | No limit | 30 to 730 days | Data retention beyond 31 days is available for additional charges. Learn more about [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor). Access to use tier is limited to subscriptions that contained a Log Analytics workspace or Application Insights resource on April 2, 2018, or are linked to an Enterprise Agreement that started before February 1, 2019 and is still active.|
22+
| [Legacy Free tier](https://docs.microsoft.com/azure/azure-monitor/logs/cost-logs#free-trial-pricing-tier)<br>(introduced April 2016) | 500 MB | 7 days | When your workspace reaches the 500 MB per day limit, data ingestion stops and resumes at the start of the next day. A day is based on UTC. Data collected by Microsoft Defender for Cloud isn't included in this 500 MB per day limit and will continue to be collected above this limit. Creating new workspaces in, or moving existing workspaces into, the legacy Free Trial pricing tier is possible only until July 1, 2022. |
23+
| [Legacy Standard tier](https://docs.microsoft.com/azure/azure-monitor/logs/cost-logs#standard-and-premium-pricing-tiers) | No limit | 30 days | Retention can't be adjusted. This tier has not been available to any new workspaces since October 1, 2016.|
24+
| [Legacy Premium tier](https://docs.microsoft.com/azure/azure-monitor/logs/cost-logs#standard-and-premium-pricing-tiers) | No limit | 365 days | Retention can't be adjusted. This tier has not been available to any new workspaces since October 1, 2016.|
2425

2526
**Number of workspaces per subscription.**
2627

2728
| Pricing tier | Workspace limit | Comments
2829
|:---|:---|:---|
29-
| Free tier | 10 | This limit can't be increased. |
30+
| Legacy Free tier | 10 | This limit can't be increased. Creating new workspaces in, or moving existing workspaces into, the legacy Free Trial pricing tier is possible only until July 1, 2022. |
3031
| All other tiers | No limit | You're limited by the number of resources within a resource group and the number of resource groups per subscription. |
3132

3233
**Azure portal**

0 commit comments

Comments
 (0)