Skip to content

Commit d73fc4c

Browse files
Stacyrch140Stacyrch140
authored
Merge pull request #247456 from MicrosoftDocs/main
Publish to live, Sunday 4:00PM PDT, 8/6
2 parents e67d8dd + 86fda0b commit d73fc4c

File tree

9 files changed

+479
-49
lines changed

9 files changed

+479
-49
lines changed

‎articles/active-directory/authentication/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,8 @@
6464
href: concept-system-preferred-multifactor-authentication.md
6565
- name: Prompts and session lifetime
6666
href: concepts-azure-multi-factor-authentication-prompts-session-lifetime.md
67+
- name: Regional opt-in
68+
href: concept-mfa-regional-opt-in.md
6769
- name: Data residency
6870
href: concept-mfa-data-residency.md
6971
- name: Licenses

‎articles/active-directory/authentication/concept-mfa-regional-opt-in.md

Lines changed: 202 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,202 @@
1+
---
2+
title: Regions that need to opt in for Azure AD Multi-Factor Authentication (MFA) telephony verification | Azure Active Directory
3+
description: To protect customers, some regions require a support ticket to request to opt in to receive MFA telephony verification Azure Active Directory
4+
5+
services: active-directory
6+
ms.service: active-directory
7+
ms.subservice: authentication
8+
ms.topic: conceptual
9+
ms.date: 08/02/2023
10+
11+
author: aloom3
12+
ms.author: justinha
13+
manager: amycolannino
14+
ms.reviewer: aloom3
15+
16+
ms.collection: M365-identity-device-management
17+
ms.custom: references_regions
18+
---
19+
# Regions that need to opt in for MFA telephony verification
20+
21+
As a protection for our customers, Microsoft doesn't automatically support telephony verification for certain region codes. If you want to receive traffic from phone numbers with these region codes, your administrator must submit a support ticket and request to opt in.
22+
23+
## Why this protection is needed
24+
25+
In today's digital world, telecommunication services have become ingrained into our lives. But advancements come with a risk of fraudulent activities. International Revenue Share Fraud (IRSF) is a threat with severe financial implications that also makes using services more difficult. Let's look at IRSF fraud more in-depth.
26+
27+
IRSF is a type of telephony fraud where criminals exploit the billing system of telecommunication services providers to make profit for themselves. Bad actors gain unauthorized access to a telecommunication network and divert traffic to those networks to skim profit for every transaction that is sent to that network. To divert traffic, bad actors steal existing usernames and passwords, create new usernames and passwords, or try a host of other things to send SMS messages and voice calls through their telecommunication network. Bad actors take advantage of multifactor authentication screens, which require an SMS or voice call before a user can access their account. This activity causes exorbitant charges and makes services unreliable for our customers, causing downtime, and system errors.
28+
29+
Here's how an IRSF attack may happen:
30+
31+
1. A bad actor first gets premium rate phone numbers and registers them.
32+
1. A bad actor uses automated scripts to request voice calls or SMS messages. The bad actor is colluding with number providers and the telecommunication network to drive more traffic to those services. The bad actor skims some of the profits of the increased traffic.
33+
1. A bad actor will hop around different region codes to continue to drive traffic and make it hard for them to get caught.
34+
35+
The most common way to conduct IRSF is through an end-user experience that requires a two-factor authentication code. Bad actors add those premium rate phone numbers and pump traffic to them by requesting two-factor authentication codes. This activity results in revenue-skimming, and can lead to billions of dollars in loss.
36+
37+
IRSF poses a significant threat to online businesses and can cause reputational damage. By understanding IRSF, you can be more aware of the problem and can engage in implementing preventive measures such as regional restrictions, rate limiting, and phone number verification.
38+
39+
## SMS verification
40+
41+
For SMS verification, the following region codes require an opt-in.
42+
43+
| Region Code | Region Name |
44+
|:----------- |:---------------------------------------------- |
45+
| 222 | Mauritania |
46+
| 998 | Uzbek |
47+
48+
## Voice verification
49+
For Voice verification, the following region codes require an opt-in.
50+
51+
| Region Code | Region Name |
52+
|:----------- |:---------------------------------------------- |
53+
| 53 | Cuba |
54+
| 58 | Venezuela |
55+
| 93 | Afghanistan |
56+
| 94 | Sri Lanka |
57+
| 95 | Myanmar (Burma) |
58+
| 98 | Iran |
59+
| 211 | South Sudan |
60+
| 212 | Morocco |
61+
| 213 | Algeria |
62+
| 216 | Tunisia |
63+
| 218 | Libya |
64+
| 220 | Gambia |
65+
| 221 | Senegal |
66+
| 222 | Mauritania |
67+
| 223 | Mali |
68+
| 224 | Guinea |
69+
| 225 | Cote d'Ivoire |
70+
| 226 | Burkina Faso |
71+
| 227 | Niger |
72+
| 228 | Togo |
73+
| 229 | Benin |
74+
| 231 | Liberia |
75+
| 232 | Sierra Leone |
76+
| 233 | Ghana |
77+
| 235 | Chad |
78+
| 236 | Central African Republic |
79+
| 237 | Cameroon |
80+
| 238 | Cabo Verde |
81+
| 239 | Sao Tome and Principe |
82+
| 240 | Equatorial Guinea |
83+
| 241 | Gabon |
84+
| 242 | Congo |
85+
| 243 | Congo |
86+
| 244 | Angola |
87+
| 245 | Guinea-Bissau |
88+
| 246 | British Indian Ocean Territory |
89+
| 247 | Ascension Island |
90+
| 248 | Seychelles |
91+
| 249 | Sudan |
92+
| 250 | Rwanda |
93+
| 251 | Ethiopia |
94+
| 252 | Somalia |
95+
| 253 | Djibouti |
96+
| 254 | Kenya |
97+
| 255 | Tanzania |
98+
| 256 | Uganda |
99+
| 257 | Burundi |
100+
| 258 | Mozambique |
101+
| 260 | Zambia |
102+
| 261 | Madagascar |
103+
| 262 | Mayotte |
104+
| 263 | Zimbabwe |
105+
| 265 | Malawi |
106+
| 266 | Lesotho |
107+
| 267 | Botswana |
108+
| 268 | Antigua and Barbuda |
109+
| 269 | Comoros |
110+
| 290 | Saint Helena, Ascension, and Tristan da Cunha |
111+
| 291 | Eritrea |
112+
| 297 | Aruba |
113+
| 299 | Greenland |
114+
| 350 | Gibraltar |
115+
| 355 | Albania |
116+
| 356 | Malta |
117+
| 359 | Bulgaria |
118+
| 370 | Lithuania |
119+
| 371 | Latvia |
120+
| 372 | Estonia |
121+
| 373 | Moldova |
122+
| 374 | Armenia |
123+
| 375 | Belarus |
124+
| 376 | Andorra |
125+
| 377 | Monaco |
126+
| 381 | Serbia |
127+
| 382 | Montenegro |
128+
| 383 | Kosovo |
129+
| 385 | Croatia |
130+
| 386 | Slovenia |
131+
| 387 | Bosnia and Herzegovina |
132+
| 389 | North Macedonia |
133+
| 500 | Falkland Islands |
134+
| 501 | Belize |
135+
| 502 | Guatemala |
136+
| 503 | El Salvador |
137+
| 504 | Honduras |
138+
| 505 | Nicaragua |
139+
| 507 | Panama |
140+
| 508 | Saint Pierre and Miquelon |
141+
| 509 | Haiti |
142+
| 591 | Bolivia |
143+
| 592 | Guyana |
144+
| 593 | Ecuador |
145+
| 594 | French Guiana |
146+
| 597 | Suriname |
147+
| 598 | Uruguay |
148+
| 670 | Timor-Leste |
149+
| 672 | Antarctica |
150+
| 674 | Nauru |
151+
| 675 | Papua New Guinea |
152+
| 676 | Tonga |
153+
| 677 | Solomon Islands |
154+
| 678 | Vanuatu |
155+
| 681 | Wallis and Futuna |
156+
| 682 | Cook Islands |
157+
| 683 | Niue |
158+
| 685 | Samoa |
159+
| 686 | Kiribati |
160+
| 687 | New Caledonia |
161+
| 689 | French Polynesia |
162+
| 690 | Tokelau |
163+
| 691 | Micronesia |
164+
| 692 | Marshall Islands |
165+
| 856 | Laos |
166+
| 960 | Maldives |
167+
| 961 | Lebanon |
168+
| 962 | Jordan |
169+
| 963 | Syria |
170+
| 964 | Iraq |
171+
| 967 | Yemen |
172+
| 968 | Oman |
173+
| 973 | Bahrain |
174+
| 974 | Qatar |
175+
| 975 | Bhutan |
176+
| 976 | Mongolia |
177+
| 977 | Nepal |
178+
| 992 | Tajikistan |
179+
| 993 | Turkmenistan |
180+
| 994 | Azerbaijan |
181+
| 995 | Georgia |
182+
| 996 | Kyrgyzstan |
183+
| 998 | Uzbekistan |
184+
| 1242 | Bahamas |
185+
| 1264 | Anguilla |
186+
| 1268 | Antigua and Barbuda |
187+
| 1284 | British Virgin Islands |
188+
| 1345 | Cayman Islands |
189+
| 1473 | Grenada |
190+
| 1649 | Turks and Caicos Islands |
191+
| 1664 | Montserrat |
192+
| 1721 | Sint Maarten |
193+
| 1758 | Saint Lucia |
194+
| 1809 | Dominica |
195+
| 1829 | Dominican Republic |
196+
| 1849 | Dominican Republic |
197+
| 1869 | Saint Kitts and Nevis |
198+
| 1876 | Jamaica |
199+
200+
## Next steps
201+
202+
* [Authentication methods in Azure Active Directory](concept-authentication-authenticator-app.md)

‎articles/ai-services/openai/concepts/models.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -81,8 +81,8 @@ These models can only be used with the Chat Completion API.
8181
| --- | --- | --- | --- | --- |
8282
| `gpt-4` <sup>1,</sup><sup>2</sup> (0314) | | N/A | 8,192 | September 2021 |
8383
| `gpt-4-32k` <sup>1,</sup><sup>2</sup> (0314) | | N/A | 32,768 | September 2021 |
84-
| `gpt-4` <sup>1</sup><sup>3</sup> (0613) | Canada East, East US, East US 2, France Central, Japan East, UK South | N/A | 8,192 | September 2021 |
85-
| `gpt-4-32k` <sup>1</sup><sup>3</sup> (0613) | Canada East, East US, East US 2, France Central, Japan East, UK South | N/A | 32,768 | September 2021 |
84+
| `gpt-4` <sup>1</sup><sup>3</sup> (0613) | Australia East, Canada East, East US, East US 2, France Central, Japan East, UK South | N/A | 8,192 | September 2021 |
85+
| `gpt-4-32k` <sup>1</sup><sup>3</sup> (0613) | Australia East, Canada East, East US, East US 2, France Central, Japan East, UK South | N/A | 32,768 | September 2021 |
8686

8787
<sup>1</sup> The model is [only available by request](https://aka.ms/oai/get-gpt4).<br>
8888
<sup>2</sup> Version `0314` of gpt-4 and gpt-4-32k will be retired no earlier than July 5, 2024. See [model updates](#model-updates) for model upgrade behavior.<br>
@@ -95,8 +95,8 @@ GPT-3.5 Turbo is used with the Chat Completion API. GPT-3.5 Turbo (0301) can als
9595
| Model ID | Base model Regions | Fine-Tuning Regions | Max Request (tokens) | Training Data (up to) |
9696
| --------- | --------------------- | ------------------- | -------------------- | ---------------------- |
9797
| `gpt-35-turbo`<sup>1</sup> (0301) | East US, France Central, South Central US, UK South, West Europe | N/A | 4,096 | Sep 2021 |
98-
| `gpt-35-turbo` (0613) | Canada East, East US, East US 2, France Central, Japan East, North Central US, UK South | N/A | 4,096 | Sep 2021 |
99-
| `gpt-35-turbo-16k` (0613) | Canada East, East US, East US 2, France Central, Japan East, North Central US, UK South | N/A | 16,384 | Sep 2021 |
98+
| `gpt-35-turbo` (0613) | Australia East, Canada East, East US, East US 2, France Central, Japan East, North Central US, UK South | N/A | 4,096 | Sep 2021 |
99+
| `gpt-35-turbo-16k` (0613) | Australia East, Canada East, East US, East US 2, France Central, Japan East, North Central US, UK South | N/A | 16,384 | Sep 2021 |
100100

101101
<sup>1</sup> Version `0301` of gpt-35-turbo will be retired no earlier than July 5, 2024. See [model updates](#model-updates) for model upgrade behavior.
102102

‎articles/azure-monitor/logs/data-retention-archive.md

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,9 +13,15 @@ Retention policies define when to remove or archive data in a [Log Analytics wor
1313

1414
This article describes how to configure data retention and archiving.
1515

16-
## Permissions
17-
18-
To configure set data retention and archiving, you must have at least [contributor rights](../logs/manage-access.md#azure-rbac).
16+
## Permissions required
17+
18+
| Action | Permissions required |
19+
|:-------|:---------------------|
20+
| Configure data retention and archive policies for a Log Analytics workspace | `Microsoft.OperationalInsights/workspaces/write` and `microsoft.operationalinsights/workspaces/tables/write` permissions to the Log Analytics workspace, as provided by the [Log Analytics Contributor built-in role](./manage-access.md#log-analytics-contributor), for example |
21+
| Get the retention and archive policy by table for a Log Analytics workspace | `Microsoft.OperationalInsights/workspaces/tables/read` permissions to the Log Analytics workspace, as provided by the [Log Analytics Reader built-in role](./manage-access.md#log-analytics-reader), for example |
22+
| Purge data from a Log Analytics workspace | `Microsoft.OperationalInsights/workspaces/purge/action` permissions to the Log Analytics workspace, as provided by the [Log Analytics Contributor built-in role](./manage-access.md#log-analytics-contributor), for example |
23+
| Set data retention for a classic Application Insights resource | `microsoft.insights/components/write` permissons to the classic Application Insights resource, as provided by the [Application Insights Component Contributor built-in role](../../role-based-access-control/built-in-roles.md#application-insights-component-contributor), for example |
24+
| Purge data from a classic Application Insights resource | `Microsoft.Insights/components/purge/action` permissions to the classic Application Insights resource, as provided by the [Application Insights Component Contributor built-in role](../../role-based-access-control/built-in-roles.md#application-insights-component-contributor), for example |
1925

2026
## How retention and archiving work
2127

‎articles/azure-monitor/logs/ingest-logs-event-hub.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ To create a custom table into which to ingest events, in the Azure portal:
7878
:::image type="content" source="media/ingest-logs-event-hub/create-custom-table-open-cloud-shell.png" lightbox="media/ingest-logs-event-hub/create-custom-table-open-cloud-shell.png" alt-text="Screenshot showing how to open Cloud Shell.":::
7979

8080

81-
1. Run this PowerShell command to create the table, providing the table name (`<table_name>`) in the JSON, and setting the `<subscription_id>`, `<resource_group_name>`, `<workspace_name>`, and `<table_name>` values in the `Invoke-AzRestMethod -Path` command:
81+
1. Run this PowerShell command to create the table, providing the table name (`<table_name>`) in the JSON (that too with suffix *_CL* in case of custom table), and setting the `<subscription_id>`, `<resource_group_name>`, `<workspace_name>`, and `<table_name>` values in the `Invoke-AzRestMethod -Path` command:
8282

8383
```PowerShell
8484
$tableParams = @'

0 commit comments

Comments
 (0)