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
1. Under **Implicit grant and hybrid flows**, select **ID tokens** and select **Save**.
77
76
1. In the left menu, under **Manage**, select **Token configuration** > **+ Add optional claim**.
78
77
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**.
79
78
1. When prompted, select **Turn on the Microsoft Graph email, profile permission**. Select **Add**.
@@ -1351,19 +1350,11 @@ The `telemetry` section of a feature flag has the following properties:
1351
1350
| Property | Description |
1352
1351
|----------------|----------------|
1353
1352
|`enabled`| Specifies whether telemetry should be published for the feature flag. |
1354
-
|`metadata`|A collection of key-value pairs, modeled as a dictionary, that can be used to attach custom metadata about the feature flag to evaluation events. |
1353
+
|`metadata`|A collection of key-value pairs, modeled as a dictionary, which can be used to attach custom metadata about the feature flag to evaluation events. |
1355
1354
1356
1355
### Custom Telemetry Publishing
1357
1356
1358
-
The feature manager has its own `ActivitySource` named "Microsoft.FeatureManagement". If`telemetry` is enabled for a feature flag, whenever the evaluation of the feature flag is started, the feature manager will start an `Activity`. When the feature flag evaluation is finished, the feature manager will add an `ActivityEvent` named `"FeatureFlag"` to the current activity. The`"FeatureFlag"`event will have tags which include the information about the feature flag evaluation. Specifically, the tags will include the following fields:
1359
-
1360
-
| Tag | Description |
1361
-
|----------------|----------------|
1362
-
|`FeatureName`| The feature flag name. |
1363
-
|`Enabled`| Whether the feature flag is evaluated as enabled. |
1364
-
|`Variant`| The assigned variant. |
1365
-
|`VariantAssignmentReason`| The reason why the variant is assigned. |
1366
-
|`TargetingId`| The user id used for targeting. |
1357
+
The feature manager has its own `ActivitySource` named "Microsoft.FeatureManagement". If`telemetry` is enabled for a feature flag, whenever the evaluation of the feature flag is started, the feature manager will start an `Activity`. When the feature flag evaluation is finished, the feature manager will add an `ActivityEvent` named `FeatureFlag` to the current activity. The`FeatureFlag`event will have tags which include the information about the feature flag evaluation, following the fields defined in the [FeatureEvaluationEvent](https://github.com/microsoft/FeatureManagement/tree/main/Schema/FeatureEvaluationEvent) schema.
1367
1358
1368
1359
> [!NOTE]
1369
1360
> All key value pairs specified in`telemetry.metadata`of the feature flag will also be included in the tags.
| 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|
156
164
157
165
> [!NOTE]
158
166
> 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.
Copy file name to clipboardExpand all lines: articles/backup/backup-reports-email.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Email Azure Backup Reports
3
3
description: Create automated tasks to receive periodic reports via email
4
4
ms.topic: how-to
5
-
ms.date: 09/11/2024
5
+
ms.date: 09/20/2024
6
6
ms.service: azure-backup
7
7
author: AbhishekMallick-MS
8
8
ms.author: v-abhmallick
@@ -89,7 +89,7 @@ When attempting to authorize the Microsoft 365 API connection, you might see an
89
89
90
90
This error can occur if the mailbox is on a dedicated Microsoft Exchange Server and isn't a valid Office 365 mailbox. [Learn more](/connectors/office365/#common-errors)
91
91
92
-
To get a valid Office 365 mailbox, submit a request to your Exchange or Global administrator to migrate the mailbox account. Users who don't have administrator permissions can't migrate accounts. For information on how to migrate the mailbox account, see [How to migrate mailbox data by using the Exchange Admin Center in Office 365](/exchange/troubleshoot/move-or-migrate-mailboxes/migrate-data-with-admin-center).
92
+
To get a valid Office 365 mailbox, submit a request to your Exchange administrator to migrate the mailbox account. Users who don't have administrator permissions can't migrate accounts. For information on how to migrate the mailbox account, see [How to migrate mailbox data by using the Exchange Admin Center in Office 365](/exchange/troubleshoot/move-or-migrate-mailboxes/migrate-data-with-admin-center).
93
93
94
94
### Scenario 4: Error in authorizing Azure Monitor Logs connection
Copy file name to clipboardExpand all lines: articles/communication-services/concepts/service-limits.md
+20-6Lines changed: 20 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,19 @@ Before acquiring a phone number, make sure your subscription meets the [geograph
49
49
50
50
For more information, see the [phone number types](./telephony/plan-solution.md) concept page and the [telephony concept](./telephony/telephony-concept.md) overview page.
51
51
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.
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.
117
131
118
132
### Send attachments larger than 10 MB
119
133
@@ -259,4 +273,4 @@ When you implement error handling, use the HTTP error code 429 to detect throttl
259
273
You can find more information on Microsoft Graph [throttling](/graph/throttling) limits in the [Microsoft Graph](/graph/overview) documentation.
260
274
261
275
## Next steps
262
-
See the [help and support](../support.md) options.
276
+
See the [help and support](../support.md) options.
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.
0 commit comments