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/communication-services/quickstarts/telephony/includes/phone-numbers-az-cli.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,6 +43,9 @@ Make these replacements in the code:
43
43
- Replace `<purchasedPhoneNumber>` with a phone number that's associated with your Communication Services resource.
44
44
- Replace `<yourConnectionString>` with your connection string.
45
45
46
+
> [!NOTE]
47
+
> The Azure CLI option provides functionality only for listing and showing phone numbers. It does not support other operations such as searching, purchasing, editing or releasing phone numbers.
48
+
46
49
### (Optional) Use Azure CLI phone numbers operations without passing in a connection string
47
50
48
51
You can configure the `AZURE_COMMUNICATION_CONNECTION_STRING` environment variable to use Azure CLI phone numbers operations without having to use `--connection_string` to pass in the connection string. To configure an environment variable, open a console window and select your operating system from the below tabs. Replace `<yourConnectionString>` with your actual connection string.
After you add the environment variable, run `source ~/.bash_profile` from your console window to make the changes effective. If you created the environment variable with your IDE open, you may need to close and reopen the editor, IDE, or shell in order to access the variable.
Copy file name to clipboardExpand all lines: articles/cosmos-db/role-based-access-control.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
@@ -26,7 +26,7 @@ The following are the built-in roles supported by Azure Cosmos DB:
26
26
|**Built-in role**|**Description**|
27
27
|---------|---------|
28
28
|[DocumentDB Account Contributor](../role-based-access-control/built-in-roles.md#documentdb-account-contributor)|Can manage Azure Cosmos DB accounts.|
29
-
|[Cosmos DB Account Reader](../role-based-access-control/built-in-roles.md#cosmos-db-account-reader-role)|Can read Azure Cosmos DB account data.|
29
+
|[Cosmos DB Account Reader Role](../role-based-access-control/built-in-roles.md#cosmos-db-account-reader-role)|Can read Azure Cosmos DB account data.|
30
30
|[CosmosBackupOperator](../role-based-access-control/built-in-roles.md#cosmosbackupoperator)| Can submit a restore request in the Azure portal for a periodic backup enabled database or a container. Can modify the backup interval and retention in the Azure portal. Cannot access any data or use Data Explorer. |
31
31
|[CosmosRestoreOperator](../role-based-access-control/built-in-roles.md#cosmosrestoreoperator)| Can perform a restore action for an Azure Cosmos DB account with continuous backup mode.|
32
32
|[Cosmos DB Operator](../role-based-access-control/built-in-roles.md#cosmos-db-operator)|Can provision Azure Cosmos DB accounts, databases, and containers. Cannot access any data or use Data Explorer.|
This article helps you configure ExpressRoute Global Reach using PowerShell. For more information, see [ExpressRouteRoute Global Reach](expressroute-global-reach.md).
15
+
This article helps you configure ExpressRoute Global Reach using PowerShell. For more information, see [ExpressRoute Global Reach](expressroute-global-reach.md).
Copy file name to clipboardExpand all lines: articles/virtual-machines/fasv6-falsv6-series.md
+22-17Lines changed: 22 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Fasv6, Falsv6 and Famsv6-series
2
+
title: Falsv6, Fasv6, and Famsv6-series
3
3
description: Specifications for Fasv6, Falsv6 and Famsv6
4
4
author: iamwilliew
5
5
ms.author: wwilliams
@@ -9,17 +9,22 @@ ms.topic: conceptual
9
9
ms.date: 01/29/2024
10
10
---
11
11
12
-
# Fasv6, Falsv6 and Famsv6-series (Preview)
12
+
# Falsv6, Fasv6, and Famsv6-series (Preview)
13
13
14
14
**Applies to:** ✔️ Linux VMs ✔️ Windows VMs ✔️ Flexible scale sets ✔️ Uniform scale sets
15
15
16
16
> [!Important]
17
17
> Azure Virtual Machine Series Falsv6, Fasv6, and Famsv6 are currently in PREVIEW. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
18
18
19
-
The Falsv6, Fasv6, and Famsv6-series utilize AMD's 4th Generation EPYC<sup>TM</sup> 9004 processor that can achieve a boosted maximum frequency of 3.7GHz with up to 320 MB L3 cache. The Falsv6, Fasv6, and Famsv6 VM series come without Simultaneous Multithreading (SMT), meaning a vCPU is now mapped to a full physical core, allowing software processes to run on dedicated and uncontested resources. These new full core VMs will suit workloads demanding the highest CPU performance. Falsv6, Fasv6, and Famsv6-series offer up to 64 full core vCPUs and 512 GiB of RAM in three memory to core ratios, and are optimized for scientific simulations, financial and risk analysis, gaming, rendering and other workloads able to take advantage of the exceptional performance. Customers running software licensed on per-vCPU basis can leverage these VMs to optimize compute costs within their infrastructure.
19
+
The Falsv6, Fasv6, and Famsv6-series utilize AMD's 4th Generation EPYC<sup>TM</sup> 9004 processor that can achieve a boosted maximum frequency of 3.7GHz with up to 320 MB L3 cache. The Falsv6, Fasv6, and Famsv6 VM series come without Simultaneous Multithreading (SMT), meaning a vCPU is now mapped to a full physical core, allowing software processes to run on dedicated and uncontested resources. These new full core VMs will suit workloads demanding the highest CPU performance.
20
+
21
+
Falsv6, Fasv6, and Famsv6-series offer up to 64 full core vCPUs and 512 GiB of RAM in three memory to core ratios, and are optimized for scientific simulations, financial and risk analysis, gaming, rendering and other workloads able to take advantage of the exceptional performance. Customers running software licensed on per-vCPU basis can leverage these VMs to optimize compute costs within their infrastructure.
20
22
21
23
> [!NOTE]
22
-
> For frequently asked questions, see **[Azure VM sizes with no local temp disk](./azure-vms-no-temp-disk.yml)**. The Falsv6, Fasv6, and Famsv6-series virtual machines do not have any temporary storage. You can attach Standard SSD, Standard HDD, and Premium SSD disk types. You can also attach Ultra Disk storage based on its regional availability. Disk storage is billed separately from virtual machines. [See pricing for disks](https://azure.microsoft.com/pricing/details/managed-disks/). The new Falsv6, Fasv6, and Famsv6 VM series will only work on OS images that are tagged with NVMe support. If your current OS image is not supported for NVMe, you’ll see an error message. NVMe support is available in 50+ of the most popular OS images, and we continuously improve the OS image coverage. Please refer to our up-to-date [lists](./enable-nvme-interface.md) for information on which OS images are tagged as NVMe supported. For more information on NVMe enablement, see our [FAQ](./enable-nvme-faqs.yml).
24
+
>
25
+
> For frequently asked questions, see **[Azure VM sizes with no local temp disk](/azure/virtual-machines/azure-vms-no-temp-disk)**. The Falsv6, Fasv6, and Famsv6-series virtual machines do not have any temporary storage. You can attach Standard SSD, Standard HDD, and Premium SSD disk types. You can also attach Ultra Disk storage based on its regional availability. Disk storage is billed separately from virtual machines. [See pricing for disks](https://azure.microsoft.com/pricing/details/managed-disks/).
26
+
>
27
+
> The new Falsv6, Fasv6, and Famsv6 VM series will only work on OS images that are tagged with NVMe support. If your current OS image is not supported for NVMe, you’ll see an error message. NVMe support is available in 50+ of the most popular OS images, and we continuously improve the OS image coverage. Please refer to our up-to-date [lists](enable-nvme-interface.md) for information on which OS images are tagged as NVMe supported. For more information on NVMe enablement, see our [FAQ](enable-nvme-faqs.yml).
23
28
>
24
29
> The new Falsv6, Fasv6, and Famsv6VM series virtual machines public preview now available. For more information and to sign up for the preview, please visit our [announcement](https://techcommunity.microsoft.com/t5/azure-compute-blog/public-preview-new-amd-based-vms-with-increased-performance/ba-p/3981351) and follow the link to the [sign-up form](https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGGr0GRqy180BHbR9RmLSiOpIpImo4Q01A_jJlUM1ZSRVlYU04wMUJQVjNQRFZHQzdEVFc1VyQlQCN0PWcu). This is an opportunity to experience our latest innovation.
25
30
@@ -32,7 +37,19 @@ The Falsv6, Fasv6, and Famsv6-series utilize AMD's 4th Generation EPYC<sup>TM</s
32
37
[Ephemeral OS Disks](/azure/virtual-machines/ephemeral-os-disks): Not Supported
| Size | vCPU | Memory: GiB | Local NVMe Temporary storage (SSD) GiB | Max data disks | Max uncached Premium SSD disk throughput: IOPS/MBps | Max burst uncached Premium SSD disk throughput: IOPS/MBps<sup>1</sup> | Max uncached Ultra Disk and Premium SSD V2 disk throughput: IOPS/MBps | Max burst uncached Ultra Disk and Premium SSD V2 disk throughput: IOPS/MBps<sup>1</sup> | Max NICs | Max network bandwidth (Mbps) |
| Size | vCPU | Memory: GiB | Local NVMe Temporary storage (SSD) GiB | Max data disks | Max uncached Premium SSD disk throughput: IOPS/MBps | Max burst uncached Premium SSD disk throughput: IOPS/MBps<sup>1</sup> | Max uncached Ultra Disk and Premium SSD V2 disk throughput: IOPS/MBps | Max burst uncached Ultra Disk and Premium SSD V2 disk throughput: IOPS/MBps<sup>1</sup> | Max NICs | Max network bandwidth (Mbps) |
| Size | vCPU | Memory: GiB | Local NVMe Temporary storage (SSD) GiB | Max data disks | Max uncached Premium SSD disk throughput: IOPS/MBps | Max burst uncached Premium SSD disk throughput: IOPS/MBps<sup>1</sup> | Max uncached Ultra Disk and Premium SSD V2 disk throughput: IOPS/MBps | Max burst uncached Ultra Disk and Premium SSD V2 disk throughput: IOPS/MBps<sup>1</sup> | Max NICs | Max network bandwidth (Mbps) |
| Size | vCPU | Memory: GiB | Local NVMe Temporary storage (SSD) GiB | Max data disks | Max uncached Premium SSD disk throughput: IOPS/MBps | Max burst uncached Premium SSD disk throughput: IOPS/MBps<sup>1</sup> | Max uncached Ultra Disk and Premium SSD V2 disk throughput: IOPS/MBps | Max burst uncached Ultra Disk and Premium SSD V2 disk throughput: IOPS/MBps<sup>1</sup> | Max NICs | Max network bandwidth (Mbps) |
0 commit comments