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
Azure Communication Services enable you to retrieve insights and look up a specific phone number using the Azure Communication Services Number Lookup SDK. It is part of the Phone Numbers SDK and can be used to support customer service scenarios, appointment reminders, two-factor authentication, and other real-time communication needs. Azure Communication Services Number Lookup allows you to reliably retrieve number insights before engaging with end-users.
19
-
18
+
Azure Communication Services Number Lookup enables you to retrieve insights and look up a specific phone number. It's part of the Phone Numbers SDK and can be used to support customer service scenarios, appointment reminders, two-factor authentication, and other real-time communication needs. Azure Communication Services Number Lookup enables you to reliably retrieve number insights before engaging with end-users.
20
19
21
20
## Number Lookup features
22
21
23
22
Key features of Azure Communication Services Number Lookup include:
24
23
25
-
-**Simple** Our API is easy to integrate with your application. We provide detailed documentation to guide you through the process, and our team of experts is always available to assist you.
26
-
-**High Accuracy** We gather data from the most reliable suppliers to ensure that you receive accurate data. Our data is updated regularly to guarantee the highest quality possible.
27
-
-**High Velocity** Our API is designed to deliver fast and accurate data, even when dealing with high volumes of data. It is optimized for speed and performance to ensure you always receive the information you need quickly and reliably.
28
-
-**Number Capability Check** Our API provides the associated number type that generally can help determine if an SMS can be sent to a particular number. This helps to avoid frustrating attempts to send messages to non-SMS-capable numbers.
29
-
-**Carrier Details** We provide information about the country or region of destination and carrier information which helps to estimate potential costs and find alternative messaging methods (e.g., sending an email).
24
+
-**Simple:** Our API is easy to integrate with your application. We provide detailed documentation to guide you through the process. Our team of experts is always available to assist you.
25
+
26
+
-**High accuracy:** We gather data from the most reliable suppliers to ensure that you receive accurate data. Our data is updated regularly to guarantee the highest quality possible.
27
+
28
+
-**High velocity:** Our API delivers fast and accurate data, even when dealing with high volumes of data. The API is optimized for speed and performance to ensure you always receive the information you need quickly and reliably.
29
+
30
+
-**Number format:** Developers can validate national and international phone number formats to increase call or message completion.
31
+
32
+
-**Number capability check:** Our API provides the associated number type to help determine if an SMS can be sent to a particular number. This helps avoid frustrating attempts to send messages to numbers that aren't SMS capable.
33
+
34
+
-**Carrier details:** We provide information about the country or region of destination and carrier information which helps to estimate potential costs and find alternative messaging methods (such as sending an email).
30
35
31
36
## Value Proposition
32
37
33
-
The main benefits the solution will provide to Azure Communication Services customers can be summarized on the below:
34
-
-**Reduce Cost:** Optimize your communication expenses by sending messages only to phone numbers that are SMS-ready
35
-
-**Increase efficiency:** Better target customers based on subscribers’ data (name, type, location, etc.). You can also decide on the best communication channel to choose based on status (e.g., SMS or email while roaming instead of calls).
38
+
Benefits of providing this solution to Azure Communication Services customers include:
39
+
40
+
-**Reduce Cost:** Optimize your communication expenses by sending messages only to phone numbers that are SMS-ready.
41
+
42
+
-**Increase efficiency:** Better target customers based on subscribers’ data (name, type, location, and so on). Choose the best communication channel to choose based on status. For example, use SMS or email while a customer is roaming instead of a phone call.
36
43
37
44
## Key Use Cases
38
45
39
-
-**Validate the number can receive the SMS before you send it:** Check if a number has SMS capabilities or not and decide if needed to use different communication channels.
40
-
*Contoso bank collected the phone numbers of the people who are interested in their services on their site. Contoso wants to send an invite to register for the promotional offer. Contoso checks before sending the link on the offer if SMS is possible channel for the number that customer provided on the site and don’t waste money to send SMS to non mobile numbers.*
41
-
-**Estimate the total cost of an SMS campaign before you launch it:** Get the current carrier of the target number and compare that with the list of known carrier surcharges.
42
-
*Contoso, a marketing company, wants to launch a large SMS campaign to promote a product. Contoso checks the current carrier details for the different numbers he is targeting with this campaign to estimate the cost based on what Azure Communication Services is charging him.*
46
+
-**Validate the number format before placing a call or sending a message:** Validate national and international phone number format.
43
47
44
-
48
+
-**Validate the number can receive the SMS before you send it:** Check if a number has SMS capabilities and decide if you need to use a different communication channel.
45
49
46
-
## Pricing
50
+
*Contoso bank collected the phone numbers of the people who are interested in their services. Contoso wants to send an invite to register for a promotional offer. Before sending the link regarding the offer, Contoso checks whether SMS is a possible channel for each customer-provided number. Checking for SMS capability saves time and money by not sending SMS messages to non mobile numbers.*
51
+
52
+
-**Estimate the total cost of an SMS campaign before you launch it:** Get the current carrier of the target number and compare that with the list of known carrier surcharges.
47
53
54
+
*Contoso, a marketing company, wants to launch a large SMS campaign to promote a product. Contoso checks the current carrier details for the different target numbers with this campaign to estimate the cost based on Azure Communication Services pricing.*
Copy file name to clipboardExpand all lines: articles/devtest-labs/devtest-lab-create-lab.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,6 +25,7 @@ This quickstart walks you through creating a lab in Azure DevTest Labs by using
25
25
-**Resource group**: Select an existing resource group from the dropdown list, or select **Create new** to create a new resource group so it's easy to delete later.
26
26
-**Lab Name**: Enter a name for the lab.
27
27
-**Location**: If you're creating a new resource group, select an Azure region for the resource group and lab.
28
+
-**Artifacts storage account access**: You can configure whether the lab uses a User-assigned Managed Identity or a Shared Key to access the lab storage account. To use a User-assigned Managed Identity, select the appropriate managed identity from the list, otherwise select the Storage Account Shared Key option from the list.
28
29
-**Public environments**: Leave **On** for access to the [DevTest Labs public environment repository](https://github.com/Azure/azure-devtestlab/tree/master/Environments). Set to **Off** to disable access. For more information, see [Enable public environments when you create a lab](devtest-lab-create-environment-from-arm.md#set-public-environment-access-for-new-lab).
29
30
30
31
:::image type="content" source="./media/devtest-lab-create-lab/portal-create-basic-settings.png" alt-text="Screenshot of the Basic Settings tab in the Create DevTest Labs form.":::
@@ -112,4 +113,4 @@ If you created a resource group for the lab, you can now delete the resource gro
112
113
To learn how to add VMs to your lab, go on to the next article:
113
114
114
115
> [!div class="nextstepaction"]
115
-
> [Create and add virtual machines to a lab in Azure DevTest Labs](devtest-lab-add-vm.md)
116
+
> [Create and add virtual machines to a lab in Azure DevTest Labs](devtest-lab-add-vm.md)
Copy file name to clipboardExpand all lines: articles/devtest-labs/tutorial-create-custom-lab.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,6 +44,7 @@ To create a lab in Azure DevTest Labs, follow these steps.
44
44
|**Resource group**|Select an existing resource group from the dropdown list, or select **Create new** to create a new resource group so it's easy to delete later.|
45
45
|**Lab name**|Enter a name for the lab.|
46
46
|**Location**|If you're creating a new resource group, select an Azure region for the resource group and lab.|
47
+
|**Artifacts storage account access**|You can configure whether the lab uses a User-assigned Managed Identity or a Shared Key to access the lab storage account. To use a User-assigned Managed Identity, select the appropriate managed identity from the list, otherwise select the Storage Account Shared Key option from the list.|
47
48
|**Public environments**|Leave **On** for access to the [DevTest Labs public environment repository](https://github.com/Azure/azure-devtestlab/tree/master/Environments). Set to **Off** to disable access. For more information, see [Enable public environments when you create a lab](devtest-lab-create-environment-from-arm.md#set-public-environment-access-for-new-lab).|
48
49
49
50
:::image type="content" source="./media/tutorial-create-custom-lab/create-custom-lab-blade.png" alt-text="Screenshot of the Basic Settings tab of the Create DevTest Labs form.":::
@@ -162,4 +163,4 @@ If you created a resource group for the lab, you can now delete that resource gr
162
163
To learn how to access the lab and VMs as a lab user, go on to the next tutorial:
163
164
164
165
> [!div class="nextstepaction"]
165
-
> [Tutorial: Access the lab](tutorial-use-custom-lab.md)
166
+
> [Tutorial: Access the lab](tutorial-use-custom-lab.md)
Copy file name to clipboardExpand all lines: articles/operator-nexus/reference-nexus-kubernetes-cluster-sku.md
+27-19Lines changed: 27 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,33 +28,41 @@ All these SKUs are having the following characteristics:
28
28
29
29
The general purpose and performance optimized VM SKUs can be used for both worker and control plane nodes within the Azure Operator Nexus Kubernetes cluster. Memory optimized VM SKUs can only be used for worker nodes.
30
30
31
+
> [!NOTE]
32
+
> To use these VM SKUs, hardware compatibility should be considered. Operator Nexus offers two hardware options: BOM 1.7.3 and BOM 2.0 (More details [here](./reference-operator-nexus-skus.md#compute-skus)). The larger VM SKUs, specifically `NC_G56_224_v1`, `NC_P54_224_v1`, and `NC_E110_448_v1`, can only be supported on hardware BOM 2.0.
33
+
>
34
+
> Nexus Tenant Kubernetes cluster VM SKUs are compatible with BOM 2.0, enabling users to use them alongside the larger VM SKUs. However, if a user tries to use BOM 2.0-specific VM SKUs on BOM 1.7.3 compute hardware, they will encounter an "insufficient resources" error during resource creation.
35
+
31
36
## General purpose VM SKUs
32
37
33
-
| VM SKU Name | vCPU | Memory (GiB) | Root Disk (GiB) |
0 commit comments