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
Copy file name to clipboardExpand all lines: articles/active-directory/develop/msal-authentication-flows.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -132,7 +132,7 @@ In the preceding diagram:
132
132
133
133
## Implicit grant
134
134
135
-
The implicit grant has been replaced by the [authorization code flow with PCKE](scenario-spa-overview.md) as the preferred and more secure token grant flow for client-side single page-applications (SPAs). If you're building a SPA, use the authorization code flow with PKCE instead.
135
+
The implicit grant has been replaced by the [authorization code flow with PKCE](scenario-spa-overview.md) as the preferred and more secure token grant flow for client-side single page-applications (SPAs). If you're building a SPA, use the authorization code flow with PKCE instead.
136
136
137
137
Single-page web apps written in JavaScript (including frameworks like Angular, Vue.js, or React.js) are downloaded from the server and their code runs directly in the browser. Because their client-side code runs in the browser and not on a web server, they have different security characteristics than traditional server-side web applications. Prior to the availability of Proof Key for Code Exchange (PKCE) for the authorization code flow, the implicit grant flow was used by SPAs for improved responsiveness and efficiency in getting access tokens.
Copy file name to clipboardExpand all lines: articles/azure-sql/database/auditing-overview.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
@@ -42,6 +42,7 @@ You can use SQL Database auditing to:
42
42
-**Hierarchical namespace** for **Azure Data Lake Storage Gen2 storage account** is currently **not supported**.
43
43
- Enabling auditing on a paused **Azure Synapse** is not supported. To enable auditing, resume Azure Synapse.
44
44
- Auditing for **Azure Synapse SQL pools** supports default audit action groups **only**.
45
+
- When you configure the auditing in Azure SQL Server or Azure SQL Database with log destination as the storage account, the target storage account must be enabled with access to storage account keys. If the storage account is configured to use Azure AD authentication only and not configured for access key usage, the auditing cannot be configured. <!-- REST API reference: - https://docs.microsoft.com/rest/api/sql/2021-08-01-preview/server-blob-auditing-policies/create-or-update -->
45
46
46
47
47
48
#### <aid="server-vs-database-level"></a>Define server-level vs. database-level auditing policy
Copy file name to clipboardExpand all lines: articles/azure-vmware/attach-disk-pools-to-azure-vmware-solution-hosts.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,16 @@
1
1
---
2
-
title: Attach disk pools to Azure VMware Solution hosts (Preview)
3
-
description: Learn how to attach a disk pool surfaced through an iSCSI target as the VMware datastore of an Azure VMware Solution private cloud. Once the datastore is configured, you can create volumes on it and attach them to your VMware instance.
2
+
title: Attach Azure disk pools to Azure VMware Solution hosts (Preview)
3
+
description: Learn how to attach an Azure disk pool surfaced through an iSCSI target as the VMware vSphere datastore of an Azure VMware Solution private cloud. Once the datastore is configured, you can create volumes on it and consume them from your Azure VMware Solution private cloud.
4
4
ms.topic: how-to
5
5
ms.date: 11/02/2021
6
-
#Customer intent: As an Azure service administrator, I want to scale my AVS hosts using disk pools instead of scaling clusters. So that I can use block storage for active working sets and tier less frequently accessed data from vSAN to disks. I can also replicate data from on-premises or primary VMware environment to disk storage for the secondary site.
6
+
#Customer intent: As an Azure service administrator, I want to scale my AVS hosts using disk pools instead of scaling clusters. So that I can use block storage for active working sets and tier less frequently accessed data from vSAN to disks. I can also replicate data from on-premises or primary VMware vSphere environment to disk storage for the secondary site.
7
7
ms.custom: ignite-fall-2021, devx-track-azurecli
8
8
ms.devlang: azurecli
9
9
---
10
10
11
11
# Attach disk pools to Azure VMware Solution hosts (Preview)
12
12
13
-
[Azure disk pools](../virtual-machines/disks-pools.md) offer persistent block storage to applications and workloads backed by Azure Disks. You can use disks as the persistent storage for Azure VMware Solution for optimal cost and performance. For example, you can scale up by using disk pools instead of scaling clusters if you host storage-intensive workloads. You can also use disks to replicate data from on-premises or primary VMware environments to disk storage for the secondary site. To scale storage independent of the Azure VMware Solution hosts, we support surfacing [ultra disks](../virtual-machines/disks-types.md#ultra-disks), [premium SSD](../virtual-machines/disks-types.md#premium-ssds) and [standard SSD](../virtual-machines/disks-types.md#standard-ssds) as the datastores.
13
+
[Azure disk pools](../virtual-machines/disks-pools.md) offer persistent block storage to applications and workloads backed by Azure Disks. You can use disks as the persistent storage for Azure VMware Solution for optimal cost and performance. For example, you can scale up by using disk pools instead of scaling clusters if you host storage-intensive workloads. You can also use disks to replicate data from on-premises or primary VMware vSphere environments to disk storage for the secondary site. To scale storage independent of the Azure VMware Solution hosts, we support surfacing [ultra disks](../virtual-machines/disks-types.md#ultra-disks), [premium SSD](../virtual-machines/disks-types.md#premium-ssds) and [standard SSD](../virtual-machines/disks-types.md#standard-ssds) as the datastores.
14
14
15
15
>[!IMPORTANT]
16
16
>Azure disk pools on Azure VMware Solution (Preview) is currently in public preview.
Copy file name to clipboardExpand all lines: articles/azure-vmware/configure-alerts-for-azure-vmware-solution.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ The following metrics are visible through Azure Monitor Metrics.
48
48
49
49
1. Under **Condition**, select **Add condition**, and in the window that opens, selects the signal you want to create for the alert rule.
50
50
51
-
In our example, we've selected **Percentage Datastore Disk Used**, which is relevant from an [Azure VMware Solution SLA](https://aka.ms/avs/sla) perspective.
51
+
In our example, we've selected **Percentage Datastore Disk Used**, which is relevant from an [Azure VMware Solution SLA](https://azure.microsoft.com/support/legal/sla/azure-vmware/v1_1/) perspective.
52
52
53
53
:::image type="content" source="media/configure-alerts-for-azure-vmware-solution/configure-signal-logic-options.png" alt-text="Screenshot showing the Configure signal logic window with signals to create for the alert rule.":::
This article walks through the steps of how to integrate [Azure Traffic Manager](../traffic-manager/traffic-manager-overview.md) with Azure VMware Solution. The integration balances application workloads across multiple endpoints. This article also walks through the steps of how to configure Traffic Manager to direct traffic between three [Azure Application Gateway](../application-gateway/overview.md) spanning several Azure VMware Solution regions.
|[AzCopy](../../storage/common/storage-use-azcopy-v10.md)| <spanclass='green-check'>✅</span></br> | <spanclass='red-x'>❌</span> |[AzCopy on the DSVM](./dsvm-tools-ingestion.md#azcopy)|
58
-
|[Blob FUSE driver](https://github.com/Azure/azure-storage-fuse)| <spanclass='red-x'>❌</span> | <spanclass='green-check'>✅</span></br> |[blobfuse on the DSVM](./dsvm-tools-ingestion.md#blobfuse)|
58
+
|[Blob FUSE driver](https://github.com/Azure/azure-storage-fuse)| <spanclass='red-x'>❌</span> | <spanclass='red-x'>❌</span></br> |[blobfuse on the DSVM](./dsvm-tools-ingestion.md#blobfuse)|
59
59
|[Azure Cosmos DB Data Migration Tool](../../cosmos-db/import-data.md)| <spanclass='green-check'>✅</span> | <spanclass='red-x'>❌</span> |[Cosmos DB on the DSVM](./dsvm-tools-ingestion.md#azure-cosmos-db-data-migration-tool)|
0 commit comments