Skip to content

Commit eeba06d

Browse files
authored
Merge pull request #287108 from MicrosoftDocs/main
9/20/2024 AM Publish
2 parents bb2c2a9 + a8dd55b commit eeba06d

34 files changed

+324
-1783
lines changed

articles/api-management/developer-portal-wordpress-plugin.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,6 @@ In this step, create a new Microsoft Entra app. In later steps, you configure th
7373

7474
`https://<apim-instance-name>.developer.azure-api.net/`
7575

76-
1. Under **Implicit grant and hybrid flows**, select **ID tokens** and select **Save**.
7776
1. In the left menu, under **Manage**, select **Token configuration** > **+ Add optional claim**.
7877
1. On the **Add optional claim** page, select **ID** and then select the following claims: **email, family_name, given_name, onprem_sid, preferred_username, upn**. Select **Add**.
7978
1. When prompted, select **Turn on the Microsoft Graph email, profile permission**. Select **Add**.

articles/azure-vmware/architecture-private-clouds.md

Lines changed: 23 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -66,36 +66,36 @@ AV64 SKUs are available per Availability Zone, the table below lists the Azure r
6666
| Australia East | AZ03 | AV36P, AV64 | Yes |7|
6767
| Australia Southeast | AZ01 | AV36 | No | N/A |
6868
| Brazil South | AZ02 | **AV36** | No | N/A |
69-
| Canada Central | AZ02 | AV36, **AV36P,** AV64| No |7|
69+
| Canada Central | AZ02 | AV36 **AV36P,** AV64| No |7|
7070
| Canada East | N/A | AV36| No | N/A |
71-
| Central India | AZ03 | AV36P, (AV64 Planned H2 2024) | No |N/A (7 Planned H2 2024) |
72-
| Central US | AZ01 | AV36P, (AV64 Planned H2 2024) | No |N/A (7 Planned H2 2024) |
73-
| Central US | AZ02 | **AV36**, (AV64 Planned H2 2024)| No |N/A (7 Planned H2 2024) |
71+
| Central India | AZ03 | AV36P (AV64 Planned H2 2024) | No |N/A (7 Planned H2 2024) |
72+
| Central US | AZ01 | AV36P (AV64 Planned H2 2024) | No |N/A (7 Planned H2 2024) |
73+
| Central US | AZ02 | **AV36** (AV64 Planned H2 2024)| No |N/A (7 Planned H2 2024) |
7474
| Central US | AZ03 | AV36P, AV64| No |7|
75-
| East Asia | AZ01 | AV36, (AV64 Planned H2 2024)| No |N/A (7 Planned H2 2024) |
75+
| East Asia | AZ01 | AV36 (AV64 Planned H2 2024)| No |N/A (7 Planned H2 2024) |
7676
| East US | AZ01 | **AV36P**, AV64| Yes |7|
7777
| East US | AZ02 | **AV36P**, AV64 | Yes | 7 |
7878
| East US | AZ03 | **AV36**, **AV36P**, AV64 | Yes | 7 |
7979
| East US 2 | AZ01 | **AV36**, AV64 | No |7|
8080
| East US 2 | AZ02 | AV36P, **AV52**, AV64 | No | 7|
81-
| France Central | AZ01 | **AV36**, (AV64 Planned H2 2024)| No |N/A (7 Planned H2 2024) |
82-
| Germany West Central | AZ01 | AV36P, (AV64 Planned H2 2024)| Yes |N/A (7 Planned H2 2024) |
83-
| Germany West Central | AZ02 | **AV36**, (AV64 Planned H2 2024)| Yes |N/A (7 Planned H2 2024) |
81+
| France Central | AZ01 | **AV36** (AV64 Planned H2 2024)| No |N/A (7 Planned H2 2024) |
82+
| Germany West Central | AZ01 | AV36P (AV64 Planned H2 2024)| Yes |N/A (7 Planned H2 2024) |
83+
| Germany West Central | AZ02 | **AV36** (AV64 Planned H2 2024)| Yes |N/A (7 Planned H2 2024) |
8484
| Germany West Central | AZ03 | AV36, **AV36P**, AV64 | Yes |7|
85-
| Italy North | AZ03 | AV36P, (AV64 Planned H2 2024)| No |N/A (7 Planned H2 2024) |
86-
| Japan East | AZ02 | **AV36**, (AV64 Planned H2 2024)| No |N/A (7 Planned H2 2024) |
87-
| Japan West | AZ01 | **AV36**, (AV64 Planned H2 2024) | No |N/A (7 Planned H2 2024) |
85+
| Italy North | AZ03 | AV36P (AV64 Planned H2 2024)| No |N/A (7 Planned H2 2024) |
86+
| Japan East | AZ02 | **AV36** (AV64 Planned H2 2024)| No |N/A (7 Planned H2 2024) |
87+
| Japan West | AZ01 | **AV36** (AV64 Planned H2 2024) | No |N/A (7 Planned H2 2024) |
8888
| North Central US | AZ01 | **AV36**, AV64 | No |7|
8989
| North Central US | AZ02 | AV36P, AV64 | No |7|
9090
| North Europe | AZ02 | AV36, AV64 | No |7|
91-
| Qatar Central | AZ03 | AV36P, (AV64 Planned H2 2024)| No |N/A (7 Planned H2 2024) |
92-
| South Africa North | AZ03 | AV36, (AV64 Planned H2 2024) | No |N/A (7 Planned H2 2024) |
91+
| Qatar Central | AZ03 | AV36P (AV64 Planned H2 2024)| No |N/A (7 Planned H2 2024) |
92+
| South Africa North | AZ03 | AV36 (AV64 Planned H2 2024) | No |N/A (7 Planned H2 2024) |
9393
| South Central US | AZ01 | AV36, AV64 | No | 7 |
9494
| South Central US | AZ02 | **AV36P**, AV52, AV64 | No | 7 |
9595
| Southeast Asia | AZ02 | **AV36** | No | N/A |
96-
| Sweden Central | AZ01 | AV36, (AV64 Planned H2 2024)| No | N/A (7 Planned H2 2024)|
96+
| Sweden Central | AZ01 | AV36 (AV64 Planned H2 2024)| No | N/A (7 Planned H2 2024)|
9797
| Switzerland North | AZ01 | **AV36**, AV64 | No | 7 |
98-
| Switzerland North | AZ03 | AV36P, (AV64 Planned H2 2024)| No |N/A (7 Planned H2 2024) |
98+
| Switzerland North | AZ03 | AV36P (AV64 Planned H2 2024)| No |N/A (7 Planned H2 2024) |
9999
| Switzerland West | AZ01 | **AV36**, AV64 | No | 7 |
100100
| UAE North | AZ03 | AV36P | No | N/A |
101101
| UK South | AZ01 | AV36, AV36P, AV52, AV64 | Yes | 7 |
@@ -153,6 +153,14 @@ Azure VMware Solution monitors the following conditions on the host:
153153
- Hardware power status
154154
- Storage status
155155
- Connection failure
156+
157+
## Alert Codes and Remediation Table
158+
| Error Code | Error Details | Recommended Action |
159+
|--------------------|---------------------------------|---------------------|
160+
| EPC_SCSIDEVICE_SHARINGMODE | This error is encountered when a Virtual Machine is configured to use a device that prevents a maintenance operation: A device that is a SCSI controller which is engaged in bus-sharing | Follow the KB article for the removal of any SCSI controller engaged in bus-sharing attached to VMs  https://knowledge.broadcom.com/external/article?legacyId=79910 |
161+
| EPC_CDROM_EMULATEMODE | This error is encountered when CD-ROM on the Virtual Machine uses emulate mode, whose ISO image is not accessible | Follow the KB article for the removal of any CDROM mounted on customer's workload Virtual Machines in emulate mode or detach ISO. It is recommended to use Passthrough mode for mounting any CD-ROM. https://knowledge.broadcom.com/external/article?legacyId=79306 |
162+
| EPC_DATASTORE_INACCESSIBLE | This error is encountered when any external Datastore attached to AVS Private Cloud becomes inaccessible | Follow the KB article for the removal of any stale Datastore attached to cluster /azure/azure-vmware/attach-azure-netapp-files-to-azure-vmware-solution-hosts?tabs=azure-portal#performance-best-practices |
163+
| EPC_NWADAPTER_STALE | This error is encountered when connected Network interface on the Vitual Machine uses network adapter which becomes inaccessible | Follow the KB article for the removal of any stale N/W adapters attached to Virtual Machines https://knowledge.broadcom.com/external/article/318738/troubleshooting-the-migration-compatibil.html |
156164

157165
> [!NOTE]
158166
> Azure VMware Solution tenant admins must not edit or delete the previously defined VMware vCenter Server alarms because they are managed by the Azure VMware Solution control plane on vCenter Server. These alarms are used by Azure VMware Solution monitoring to trigger the Azure VMware Solution host remediation process.

articles/communication-services/.openpublishing.redirection.communication-services.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -460,6 +460,11 @@
460460
"source_path_from_root": "/articles/communication-services/concepts/advanced-messaging/message-analysis.md",
461461
"redirect_url": "/articles/communication-services/concepts/advanced-messaging/message-analysis/message-analysis.md",
462462
"redirect_document_id": false
463+
},
464+
{
465+
"source_path_from_root": "/articles/communication-services/concepts/telephony/outbound-calling.md",
466+
"redirect_url": "/azure/communication-services/concepts/telephony/toll-free-calling",
467+
"redirect_document_id": false
463468
}
464469
]
465470
}

articles/communication-services/concepts/service-limits.md

Lines changed: 20 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,19 @@ Before acquiring a phone number, make sure your subscription meets the [geograph
4949

5050
For more information, see the [phone number types](./telephony/plan-solution.md) concept page and the [telephony concept](./telephony/telephony-concept.md) overview page.
5151

52-
If you want to purchase more phone numbers or place a special order, follow the [instructions here](https://github.com/Azure/Communication/blob/master/special-order-numbers.md). If you would like to port toll-free phone numbers from external accounts to their Azure Communication Services account, follow the [instructions here](https://github.com/Azure/Communication/blob/master/port-numbers.md).
52+
Number purchase limits can be increased through a request to Azure Support.
53+
54+
1. Open the [Azure portal](https://ms.portal.azure.com/) and sign in.
55+
2. Select [Help+Support](https://ms.portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/overview).
56+
3. Click **Create new support request**.
57+
4. In the **Describe your issue** text box, enter `Technical` then click **Go**.
58+
5. From the **Select a service** dropdown menu, select **Service and Subscription Limits (Quotas)** then click **Next**.
59+
6. At the Problem description, choose the **Issue type**, **Subscription**, and **Quota type** then click **Next**.
60+
7. Review any **Recommended solution** if available, then click **Next**.
61+
8. Add **Additional details** as needed, then click **Next**.
62+
9. At **Review + create** check the information, make changes as needed, then click **Create**.
63+
64+
5365

5466
## Identity
5567

@@ -110,10 +122,12 @@ You can send a limited number of email messages. If you exceed the following lim
110122

111123
### Size Limits
112124

113-
| **Name** | Limit |
114-
|--|--|
115-
|Number of recipients in Email|50 |
116-
|Total email request size (including attachments) |10 MB |
125+
| **Name** | Limit |
126+
| --- | --- |
127+
| Number of recipients in Email | 50 |
128+
| Total email request size (including attachments) | 10 MB |
129+
130+
For all message size limits, you need to consider that that base64 encoding increases the size of the message. You need to increase the size value to account for the message size increase that occurs after the message attachments and any other binary data are Base64 encoded. Base64 encoding increases the size of the message by about 33%, so the message size is about 33% larger than the message sizes before encoding. For example, if you specify a maximum message size value of ~10 MB, you can expect a realistic maximum message size value of approximately ~7.5 MB.
117131

118132
### Send attachments larger than 10 MB
119133

@@ -259,4 +273,4 @@ When you implement error handling, use the HTTP error code 429 to detect throttl
259273
You can find more information on Microsoft Graph [throttling](/graph/throttling) limits in the [Microsoft Graph](/graph/overview) documentation.
260274

261275
## Next steps
262-
See the [help and support](../support.md) options.
276+
See the [help and support](../support.md) options.

articles/communication-services/concepts/telephony/outbound-calling.md

Lines changed: 0 additions & 20 deletions
This file was deleted.
Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
---
2+
title: Calling with toll-free numbers - Azure Communication Services
3+
description: Information about inbound and outbound calling limitations with toll-free numbers
4+
author: krkutser
5+
manager: rcole
6+
services: azure-communication-services
7+
8+
ms.author: krkutser
9+
ms.date: 03/10/2023
10+
ms.topic: conceptual
11+
ms.service: azure-communication-services
12+
ms.subservice: pstn
13+
---
14+
15+
# Outbound and inbound calling with toll-free numbers
16+
Azure Communication Services supports inbound and outbound calling capability with toll-free numbers in many countries. However, there are some common limitations that you should be aware of.
17+
18+
**Outbound calling with toll-free numbers**
19+
20+
Microsoft provides toll-free telephone numbers that have outbound calling capabilities, but it's important to note that this feature is only provided on a "best-effort" basis. In some countries/regions, toll-free numbers are considered as an "inbound only" service from regulatory perspective. This means, that in some scenarios, the receiving carrier may not allow incoming calls from toll-free telephone numbers. Since Microsoft and our carrier-partners don't have control over other carrier networks, we can't guarantee that outbound calls reach all possible destinations.
21+
22+
23+
**Inbound calls to Toll-Free numbers**
24+
25+
All of our toll-free numbers have inbound calling capability, but do note that inbound calls to your toll-free numbers are only guaranteed to work if both the Toll-Free number and the caller's phone number are from the same country. If a call to your toll-free number originates outside the toll-free number country, we can't guarantee the delivery of the call. In most cases, international reachability on our toll-free numbers is supported, but there can be certain international carrier and country combinations where we can't guarantee that the call reaches to your Toll-Free number.

articles/communication-services/toc.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -955,8 +955,8 @@ items:
955955
href: concepts/telephony/certified-session-border-controllers.md
956956
- name: Inbound telephony calling capabilities
957957
href: concepts/telephony/inbound-calling-capabilities.md
958-
- name: Outbound calling with Toll-Free numbers
959-
href: concepts/telephony/outbound-calling.md
958+
- name: Calling with toll-free numbers
959+
href: concepts/telephony/toll-free-calling.md
960960
- name: Known limitations
961961
href: concepts/telephony/known-limitations-acs-telephony.md
962962
- name: Troubleshooting

articles/data-factory/how-to-configure-azure-ssis-ir-custom-setup.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -128,17 +128,17 @@ If you select the **Install Azure PowerShell** type for your express custom setu
128128

129129
If you select the **Install licensed component** type for your express custom setup, you can then select an integrated component from our ISV partners in the **Component name** drop-down list:
130130

131-
* If you select the **SentryOne's Task Factory** component, you can install the [Task Factory](https://www.solarwinds.com/resources/it-glossary/ssis-components) suite of components from SentryOne on your Azure-SSIS IR by entering the product license key that you purchased from them in the **License key** box. The current integrated version is **2020.21.2**.
131+
* If you select the **SentryOne's Task Factory** component, you can install the [Task Factory](https://www.solarwinds.com/resources/it-glossary/ssis-components) suite of components from SentryOne on your Azure-SSIS IR by entering the product license key that you purchased from them in the **License key** box. The current integrated version is **2021.18.1**.
132132

133133
* If you select the **oh22's HEDDA.IO** component, you can install the [HEDDA.IO](https://github.com/oh22is/HEDDA.IO/tree/master/SSIS-IR) data quality/cleansing component from oh22 on your Azure-SSIS IR. To do so, you need to purchase their service beforehand. The current integrated version is **1.0.14**.
134134

135135
* If you select the **oh22's SQLPhonetics.NET** component, you can install the [SQLPhonetics.NET](https://appsource.microsoft.com/product/web-apps/oh22.sqlphonetics-ssis) data quality/matching component from oh22 on your Azure-SSIS IR. To do so, enter the product license key that you purchased from them beforehand in the **License key** text box. The current integrated version is **1.0.45**.
136136

137-
* If you select the **KingswaySoft's SSIS Integration Toolkit** component, you can install the [SSIS Integration Toolkit](https://www.kingswaysoft.com/products/ssis-integration-toolkit-for-microsoft-dynamics-365) suite of connectors for CRM/ERP/marketing/collaboration apps, such as Microsoft Dynamics/SharePoint/Project Server, Oracle/Salesforce Marketing Cloud, etc. from KingswaySoft on your Azure-SSIS IR by entering the product license key that you purchased from them in the **License key** box. The current integrated version is **21.2**.
137+
* If you select the **KingswaySoft's SSIS Integration Toolkit** component, you can install the [SSIS Integration Toolkit](https://www.kingswaysoft.com/products/ssis-integration-toolkit-for-microsoft-dynamics-365) suite of connectors for CRM/ERP/marketing/collaboration apps, such as Microsoft Dynamics/SharePoint/Project Server, Oracle/Salesforce Marketing Cloud, etc. from KingswaySoft on your Azure-SSIS IR by entering the product license key that you purchased from them in the **License key** box. The current integrated version is **23.1**.
138138

139-
* If you select the **KingswaySoft's SSIS Productivity Pack** component, you can install the [SSIS Productivity Pack](https://www.kingswaysoft.com/products/ssis-productivity-pack) suite of components from KingswaySoft on your Azure-SSIS IR by entering the product license key that you purchased from them in the **License key** box. The current integrated version is **21.2**.
139+
* If you select the **KingswaySoft's SSIS Productivity Pack** component, you can install the [SSIS Productivity Pack](https://www.kingswaysoft.com/products/ssis-productivity-pack) suite of components from KingswaySoft on your Azure-SSIS IR by entering the product license key that you purchased from them in the **License key** box. The current integrated version is **23.1**.
140140

141-
* If you select the **Theobald Software's Xtract IS** component, you can install the [Xtract IS](https://theobald-software.com/en/xtract-is/) suite of connectors for SAP system (ERP, S/4HANA, BW) from Theobald Software on your Azure-SSIS IR by dragging & dropping/uploading the product license file that you purchased from them into the **License file** box. The current integrated version is **6.5.13.18**.
141+
* If you select the **Theobald Software's Xtract IS** component, you can install the [Xtract IS](https://theobald-software.com/en/xtract-is/) suite of connectors for SAP system (ERP, S/4HANA, BW) from Theobald Software on your Azure-SSIS IR by dragging & dropping/uploading the product license file that you purchased from them into the **License file** box. The current integrated version is **6.9.3.26**.
142142

143143
* If you select the **AecorSoft's Integration Service** component, you can install the [Integration Service](https://www.aecorsoft.com/en/products/integrationservice) suite of connectors for SAP and Salesforce systems from AecorSoft on your Azure-SSIS IR. To do so, enter the product license key that you purchased from them beforehand in the **License key** text box. The current integrated version is **3.0.00**.
144144

articles/event-grid/outlook-events.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -212,7 +212,7 @@ When an event is triggered, the Event Grid service sends data about that event t
212212
"id": "00d8a100-2e92-4bfa-86e1-0056dacd0fce",
213213
"type": "Microsoft.Graph.MessageCreated",
214214
"source": "/tenants/<tenant-id>/applications/<application-id>",
215-
"subject": "Messages/<messaeg-id>",
215+
"subject": "Users/<user-id>/Messages/<messaeg-id>",
216216
"time": "2024-05-22T22:24:31.3062901Z",
217217
"datacontenttype": "application/json",
218218
"specversion": "1.0",
@@ -222,12 +222,13 @@ When an event is triggered, the Event Grid service sends data about that event t
222222
"SubscriptionExpirationDateTime": "2024-06-22T23:56:30.1307708Z",
223223
"ChangeType": "created",
224224
"subscriptionId": "MTE1MTVlYTktMjVkZS00MjY3LWI1YzYtMjg0NzliZmRhYWQ2",
225-
"resource": "https://outlook.office365.com/api/beta/Users('userId@tenantId')/Messages('<message id>')",
225+
"resource": "Users/<user-id>/Messages/<message-id>",
226226
"clientState": "<client state>",
227+
"tenantId":"<tenant-id>",
227228
"resourceData": {
228229
"Id": "<message id>",
229230
"@odata.etag": "<tag id>",
230-
"@odata.id": "https://outlook.office365.com/api/beta/Users('userId@tenantId')/Messages('<message id>')",
231+
"@odata.id": "Users/<user-id>/Messages/<message-id>",
231232
"@odata.type": "#Microsoft.OutlookServices.Message",
232233
"OtherResourceData": "<some other resource data>"
233234
}

0 commit comments

Comments
 (0)