Merge pull request #297687 from damabe/vdamabe-policheck1

Policheck Update - April 4 | Bulk Update

Author: ttorble

articles/active-directory-b2c/service-limits.md

@@ -196,7 +196,7 @@ As a protection for our customers, Microsoft places some restrictions on telepho
 | 233 |	Ghana|	10	| 30 |
 | 234 | Nigeria | 20 | 100 |
 | 236 |	Central African Republic  |	10	| 30 |
-| 238 | Cape Verde | 10 | 30 |
+| 238 | Cabo Verde | 10 | 30 |
 | 249 |  Sudan | 10  |  30  |
 | 251 |	Ethiopia  |	10	| 30 |
 | 252 |  Somalia   | 10  |  30  |  

articles/communication-services/concepts/includes/sms-ten-digit-long-code-pricing.md

@@ -19,7 +19,7 @@ ms.author: prakulka
 >- For billing locations outside the US and Puerto Rico Azure Prepayment (previously called Monetary Commitment) funds and Azure prepaid credits are not eligible for purchasing the products.
 ## 10 Digit Long Code (10DLC) Pricing
 
-This page provides an overview of the pricing for 10DLC (10-Digit Long Code) SMS services available through Azure Communication Services (ACS). 10DLC is primarily supported in the United States. Availability depends on the subscription billing location and eligibility. Check the [ACS eligibility documentation](../../concepts/numbers/phone-number-management-for-united-states.md) for more details on supported countries. The 10DLC SMS service requires registering a brand, registering a campaign, and provisioning a 10DLC number through the Azure portal. Pay-as-you-go pricing applies to these different services: brand registration, campaign registration, phone number leasing, and message usage. 
+This page provides an overview of the pricing for 10DLC (10-Digit Long Code) SMS services available through Azure Communication Services (ACS). 10DLC is primarily supported in the United States. Availability depends on the subscription billing location and eligibility. Check the [ACS eligibility documentation](../../concepts/numbers/phone-number-management-for-united-states.md) for more details on supported countries/regions. The 10DLC SMS service requires registering a brand, registering a campaign, and provisioning a 10DLC number through the Azure portal. Pay-as-you-go pricing applies to these different services: brand registration, campaign registration, phone number leasing, and message usage. 
 
 ### **Registration Fees**
 Registration fees are required for brands and campaigns to comply with U.S. 10DLC regulations. 

articles/communication-services/concepts/sms/sms-faq.md

@@ -66,9 +66,9 @@ Yes, there is a fee. Refer to the [pricing page](../sms-pricing.md) for details
 
 ## General 10DLC FAQs
 
-### Can I use 10DLC numbers in any country?
+### Can I use 10DLC numbers in any country or region?
 
-No, 10DLC is primarily supported in the United States. Availability depends on the subscription billing location and eligibility. Check the [ACS eligibility documentation](../../concepts/numbers/phone-number-management-for-united-states.md) for more details on supported countries.
+No, 10DLC is primarily supported in the United States. Availability depends on the subscription billing location and eligibility. Check the [ACS eligibility documentation](../../concepts/numbers/phone-number-management-for-united-states.md) for more details on supported countries/regions.
 
 ### What is a 10DLC number?
 A 10DLC (10-Digit Long Code) number is a standard 10-digit phone number used for Application-to-Person (A2P) messaging in the United States. It is designed for businesses to send SMS messages to customers at scale, without the restrictions of traditional long codes.

articles/communication-services/concepts/sms/sms-number-types.md

@@ -88,7 +88,7 @@ Azure Communication Services provides the following phone number types:
    - Notifications: Order updates, delivery notifications, and account-related messages.
    - Marketing: Commonly used for branding in EMEA/APAC.
 - **Regulations**
-  - Some countries require registration for using alphanumeric sender IDs.
+  - Some countries/regions require registration for using alphanumeric sender IDs.
   - Opt-Out Management: While Alphanumeric IDs are typically one-way, businesses should still provide opt-out instructions in the message content.
   - France: Alphanumeric IDs are permitted only for transactional messaging, not marketing.
   - Australia: Alphanumeric Sender IDs are permitted, but opt-out instructions should be provided.
@@ -104,11 +104,11 @@ Azure Communication Services provides the following phone number types:
 | **Two-Way Communication**    | Supported                          | Supported                           | Supported                      | Not Supported (one-way only)                |
 | **Brand Visibility**         | Low                                | Moderate (localized presence)       | High                               | High (direct brand recognition)             |
 | **Use Case Examples**        | Customer support, notifications    | Local business communications, marketing & promotions | High-volume campaigns, 2FA       | Brand visibility, one-way notifications     |
-| **Compliance Requirements**  | SMS verification, opt-out support  | Campaign registration, opt-out support | Carrier approval, opt-in proof    | Varies by country (e.g., France restricts marketing messages) |
+| **Compliance Requirements**  | SMS verification, opt-out support  | Campaign registration, opt-out support | Carrier approval, opt-in proof    | Varies by country/region (e.g., France restricts marketing messages) |
 | **Format**                   | 1-800-XXX-XXXX                     | XXX-XXX-XXXX                        | 5-6 digits                          | Up to 11 characters (letters/numbers)       |
 | **Example**                  | 1-800-555-1234                     | 212-555-6789                        | 12345                               | MYBRAND123                                  |
 
-To send messages across multiple countries, customers must request different numbers based on the number types supported in each destination.
+To send messages across multiple countries/regions, customers must request different numbers based on the number types supported in each destination.
 
 ## Next steps
 

articles/communication-services/concepts/telephony/how-to-manage-your-calling-identity.md

@@ -60,4 +60,4 @@ Once the request is approved by the carrier, it takes **48 hours to be published
 - This registration is available only for US local numbers. It doesn't support toll free numbers.
 - This service only applies to *outbound* calls for numbers that customer owns.
 - CNAM databases aren't always up to date and not consistently updated. There's a potential for misspellings.
-- There are multiple CNAM databases across the country and terminating carriers may subscribe to one or more databases.
+- There are multiple CNAM databases across the country/region and terminating carriers may subscribe to one or more databases.

articles/communication-services/concepts/telephony/try-number-lookup.md

@@ -14,7 +14,7 @@ ms.subservice: pstn
 
 # Try Number Lookup
 
-Try Number Lookup is a tool in Azure portal to help customers confirm that the phone number they want to communicate with is valid. The tool also retrieves number details to identify the country, carrier, and type. This enables developers to quickly test Azure Communication Services number lookup capabilities, without an existing app or code on their end.
+Try Number Lookup is a tool in Azure portal to help customers confirm that the phone number they want to communicate with is valid. The tool also retrieves number details to identify the country/region, carrier, and type. This enables developers to quickly test Azure Communication Services number lookup capabilities, without an existing app or code on their end.
 
 ## Prerequisites
 
@@ -23,7 +23,7 @@ Try Number Lookup is a tool in Azure portal to help customers confirm that the p
 
 ## Overview
 
-Open the [Azure portal](https://portal.azure.com/#home) and search for **Number Lookup**. Then enter a phone number that you want to look up or validate. You can either check national and international format for free, or request details about number type, country, and carrier for a fee. The tool also generates the associated code. You can select **Use my connection string** to automatically populate the `connection string` for the resource.
+Open the [Azure portal](https://portal.azure.com/#home) and search for **Number Lookup**. Then enter a phone number that you want to look up or validate. You can either check national and international format for free, or request details about number type, country/region, and carrier for a fee. The tool also generates the associated code. You can select **Use my connection string** to automatically populate the `connection string` for the resource.
 
 ![A screenshot from the Azure portal displaying the new view for the Try Number Lookup option.](../media/try-number-lookup.png)
 

articles/energy-data-services/faq-energy-data-services.yml

@@ -28,7 +28,7 @@ sections:
       questions:
         - question: Why cannot the Country Of Origin (COO) specific configuration be updated by the customer? 
           answer: >
-            The OSDU® platform does not offer APIs for making country-specific configuration changes. These configuration settings are stored in .json files within the legal service container, and any changes require a service restart to take effect. Additionally, the Azure Data Manager for Energy service architecture does not expose the underlying infrastructure to customers, preventing them from making these changes directly.
+            The OSDU® platform does not offer APIs for making country/region specific configuration changes. These configuration settings are stored in .json files within the legal service container, and any changes require a service restart to take effect. Additionally, the Azure Data Manager for Energy service architecture does not expose the underlying infrastructure to customers, preventing them from making these changes directly.
 
     - name: External Data Sources
       questions:

articles/energy-data-services/how-to-enable-legal-tags-restricted-country-of-origin.md

@@ -14,7 +14,7 @@ ms.date: 02/08/2025
 Legal tag definitions represent the legal status of the data hosted on an Azure Data Manager for Energy resource. A valid legal tag is required for data ingestion and retrieval stored on the resource. See [How to manage legal tags](how-to-manage-legal-tags.md).
 
 ## COO (Country of Origin) configuration
-The creation of legal tags is governed by a configuration hosted on each Azure Data Manager for Energy resource, defined in OSDU® as the [legal service default configuration](https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/blob/master/legal-core/src/main/resources/DefaultCountryCode.json?ref_type=heads). This is a JSON configuration that defines data residency risk for data originating from these countries using the parameter **residencyRisk** and the data types to which this risk status doesn't apply using the parameter **typesNotApplyDataResidency**. Below is a sample configuration for data originating from Australia as an example:
+The creation of legal tags is governed by a configuration hosted on each Azure Data Manager for Energy resource, defined in OSDU® as the [legal service default configuration](https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/blob/master/legal-core/src/main/resources/DefaultCountryCode.json?ref_type=heads). This is a JSON configuration that defines data residency risk for data originating from these countries/regions using the parameter **residencyRisk** and the data types to which this risk status doesn't apply using the parameter **typesNotApplyDataResidency**. Below is a sample configuration for data originating from Australia as an example:
 
 ```json
 {
@@ -26,9 +26,9 @@ The creation of legal tags is governed by a configuration hosted on each Azure D
 }
 ```
 
-The **residencyRisk** can take the values `default`, `Not Assigned`, `Embargoed`, and `No restriction`. For countries configured as `No restriction`, creating legal tags and later data ingestion is allowed. However, for all other statuses, an attempt to create legal tags would fail.
+The **residencyRisk** can take the values `default`, `Not Assigned`, `Embargoed`, and `No restriction`. For countries/regions configured as `No restriction`, creating legal tags and later data ingestion is allowed. However, for all other statuses, an attempt to create legal tags would fail.
 
-For countries with status as `default` and `Not Assigned`, the default configuration can be overridden by changing the residencyRisk to `client consent required` in a legal service configuration maintained in `Legal_COO.json`. This change in configuration is the recommended method to enable legal tags for restricted COO. As an example, Brazil’s default status doesn't allow the creation of legal tags for data ingestion with Brazil as the COO:
+For countries/regions with status as `default` and `Not Assigned`, the default configuration can be overridden by changing the residencyRisk to `client consent required` in a legal service configuration maintained in `Legal_COO.json`. This change in configuration is the recommended method to enable legal tags for restricted COO. As an example, Brazil’s default status doesn't allow the creation of legal tags for data ingestion with Brazil as the COO:
 
 ```json
 {
@@ -60,16 +60,16 @@ To enable this change, you should raise a support ticket on the Azure portal usi
 - Region in which the instance is deployed
 - Azure Data Manager for Energy developer tier resource name
 - Data partition name on which the configuration is to be changed.
-- List of country-specific configurations with new values to be applied (as shown above).
+- List of country/region specific configurations with new values to be applied (as shown above).
 
 > [!TIP]
-> Multiple partition configuration changes can be submitted in the same request by clearly specifying the partition name and the associated country-specific configuration changes.
+> Multiple partition configuration changes can be submitted in the same request by clearly specifying the partition name and the associated country/region specific configuration changes.
 
 > [!NOTE]
-> The country-specific configuration can also be reversed to the original state of 'default' or 'Not Assigned' if the customer chooses.
+> The country/region specific configuration can also be reversed to the original state of 'default' or 'Not Assigned' if the customer chooses.
 
 > [!IMPORTANT]
-> Microsoft isn't responsible for, and consults not or recommends changes to the **residencyRisk** status of country-specific configurations. The customer, by making such a request to allow data from these countries of origin by changing the configuration, is doing so at their own risk and understanding.
+> Microsoft isn't responsible for, and consults not or recommends changes to the **residencyRisk** status of country/region specific configurations. The customer, by making such a request to allow data from these countries/regions of origin by changing the configuration, is doing so at their own risk and understanding.
 
 ## Related content
 

articles/energy-data-services/release-notes.md

@@ -34,7 +34,7 @@ Azure Data Manager for Energy now includes support for the Wellbore domain servi
 Azure Data Manager for Energy has implemented performance and scale enhancements to handle ingestion and conversion of seismic datasets with higher number of vertical samples. Additionally, for consuming these datasets via seismic streaming applications, Azure Data Manager for Energy now supports up to 4x higher throughput, allowing a proportional increase in the number of consumers using SDMS APIs.
 
 ### Create legal tags for restricted COO (Country of Origin)
-OSDU® defines `residencyRisk` for data originating from certain countries in the default configuration [DefaultCountryCode.json](https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/blob/master/legal-core/src/main/resources/DefaultCountryCode.json?ref_type=heads). This configuration can now be edited in an OSDU® compliant manner to allow the creation of legal tags and the ingestion of data from such countries on Azure Data Manager for Energy. These configurations apply at a partition level. See [How to enable legal tag creation for OSDU® restricted COO (Country of Origin) data?](how-to-enable-legal-tags-restricted-country-of-origin.md) for more details.
+OSDU® defines `residencyRisk` for data originating from certain countries/regions in the default configuration [DefaultCountryCode.json](https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/blob/master/legal-core/src/main/resources/DefaultCountryCode.json?ref_type=heads). This configuration can now be edited in an OSDU® compliant manner to allow the creation of legal tags and the ingestion of data from such countries/regions on Azure Data Manager for Energy. These configurations apply at a partition level. See [How to enable legal tag creation for OSDU® restricted COO (Country of Origin) data?](how-to-enable-legal-tags-restricted-country-of-origin.md) for more details.
 
 ## November 2024
 ### SOC 2 and ISO certification