Merge pull request #218435 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: rmca14

articles/active-directory/authentication/concept-authentication-phone-options.md

@@ -52,7 +52,7 @@ With phone call verification during SSPR or Azure AD Multi-Factor Authentication
 
 ## Office phone verification
 
-With phone call verification during SSPR or Azure AD Multi-Factor Authentication, an automated voice call is made to the phone number registered by the user. To complete the sign-in process, the user is prompted to press # on their keypad. 
+With office phone call verification during SSPR or Azure AD Multi-Factor Authentication, an automated voice call is made to the phone number registered by the user. To complete the sign-in process, the user is prompted to press # on their keypad. 
 
 ## Troubleshooting phone options
 

articles/active-directory/saas-apps/sap-analytics-cloud-provisioning-tutorial.md

@@ -106,7 +106,7 @@ This section guides you through the steps to configure the Azure AD provisioning
 
 	![Screenshot of the Provisioning Mode dropdown list with the Automatic option called out.](common/provisioning-automatic.png)
 
-5. Under the **Admin Credentials** section, input the tenant URL value retrieved earlier in **Tenant URL**. Input the access token value retrieved earlier in **Secret Token**. Click **Test Connection** to ensure Azure AD can connect to InVision. If the connection fails, ensure your SAP Analytics Cloud account has Admin permissions and try again.
+5. Under the **Admin Credentials** section, input the tenant URL value retrieved earlier in **Tenant URL**. Input the access token value retrieved earlier in **Secret Token**. Click **Test Connection** to ensure Azure AD can connect to SAP Analytics Cloud. If the connection fails, ensure your SAP Analytics Cloud account has Admin permissions and try again.
 
  	![Screenshot shows the Admin Credentials dialog box, where you can enter your Tenant U R L and Secret Token.](./media/sap-analytics-cloud-provisioning-tutorial/provisioning.png)
 

articles/application-gateway/configuration-infrastructure.md

@@ -40,10 +40,10 @@ For example, here's how to calculate the available addressing for a subnet with
 - Gateway 3: Maximum of 15 instances; utilizes a private frontend IP configuration
 - Subnet Size: /24
 
-Subnet Size /24 = 255 IP addresses - 5 reserved from the platform = 250 available addresses.
-250 - Gateway 1 (10) - 1 private frontend IP configuration = 239
-239 - Gateway 2 (2) = 237
-237 - Gateway 3 (15) - 1 private frontend IP configuration = 221
+Subnet Size /24 = 256 IP addresses - 5 reserved from the platform = 251 available addresses.
+251 - Gateway 1 (10) - 1 private frontend IP configuration = 240
+240 - Gateway 2 (2) = 238
+238 - Gateway 3 (15) - 1 private frontend IP configuration = 222
 
 > [!IMPORTANT]
 > Although a /24 subnet isn't required per Application Gateway v2 SKU deployment, it is highly recommended. This is to ensure that Application Gateway v2 has sufficient space for autoscaling expansion and maintenance upgrades. You should ensure that the Application Gateway v2 subnet has sufficient address space to accommodate the number of instances required to serve your maximum expected traffic. If you specify the maximum instance count, then the subnet should have capacity for at least that many addresses. For capacity planning around instance count, see [instance count details](understanding-pricing.md#instance-count).

articles/application-gateway/configuration-listeners.md

@@ -38,7 +38,7 @@ Choose the frontend IP address that you plan to associate with this listener. Th
 
 ## Frontend port
 
-Choose the frontend port. Select an existing port or create a new one. Choose any value from the [allowed range of ports](./application-gateway-components.md#ports). You can use not only well-known ports, such as 80 and 443, but any allowed custom port that's suitable. A port can be used for public-facing listeners or private-facing listeners.
+Choose the front-end port. Select an existing port or create a new one. Choose any value from the [allowed range of ports](./application-gateway-components.md#ports). You can use not only well-known ports, such as 80 and 443, but any allowed custom port that's suitable. A port can be used for public-facing listeners or private-facing listeners, however the same port cannot be used for both at the same time.
 
 ## Protocol
 

articles/cognitive-services/language-service/concepts/model-lifecycle.md

@@ -81,11 +81,11 @@ Use the table below to find which model versions are supported by each feature:
 
 | Feature                                     | Supported Training config versions         | Training config expiration         | Deployment expiration  |
 |---------------------------------------------|--------------------------------------------|------------------------------------|------------------------|
-| Custom text classification                  | `2022-05-01`                               | `04/10/2023`                       | `04/28/2024`           |
-| Conversational language understanding       | `2022-05-01`                               | `10/28/2022`                       | `10/28/2023`           |
-| Conversational language understanding       | `2022-09-01`                               | `04/10/2023`                       | `04/28/2024`           |
-| Custom named entity recognition             | `2022-05-01`                               | `04/10/2023`                       | `04/28/2024`           |
-| Orchestration workflow                      | `2022-05-01`                               | `10/28/2022`                       | `10/28/2023`           |
+| Custom text classification                  | `2022-05-01`                               | `2023-05-01`                       | `2024-04-30`           |
+| Conversational language understanding       | `2022-05-01`                               | `2022-10-28`                       | `2023-10-28`           |
+| Conversational language understanding       | `2022-09-01`                               | `2023-02-28`                       | `2024-02-28`           |
+| Custom named entity recognition             | `2022-05-01`                               | `2023-05-01`                       | `2024-04-30`           |
+| Orchestration workflow                      | `2022-05-01`                               | `2023-05-01`                       | `2024-04-30`           |
 
 
 ## API versions

articles/cosmos-db/mongodb/quickstart-nodejs.md

@@ -231,7 +231,7 @@ The output of the app should be similar to this example:
 
 ## Clean up resources
 
-When you no longer need the Azure Cosmos DB for NoSQL account, you can delete the corresponding resource group.
+When you no longer need the Azure Cosmos DB for MongoDB account, you can delete the corresponding resource group.
 
 ### [Azure CLI](#tab/azure-cli)
 

articles/machine-learning/resource-curated-environments.md

@@ -46,8 +46,8 @@ The following configurations are supported:
 
 | Environment Name | OS | GPU Version| Python Version | PyTorch Version | ORT-training Version | DeepSpeed Version | torch-ort Version | 
 | --- | --- | --- | --- | --- | --- | --- | --- |
-| AzureML-ACPT-pytorch-1.12-py39-cuda11.6-gpu | Ubuntu 20.04  | cu116 | 3.9 | 1.13.1 | 1.12.1 | 0.7.3 | 1.13.1 |
-| AzureML-ACPT-pytorch-1.12-py38-cuda11.6-gpu | Ubuntu 20.04  | cu116 | 3.8 | 1.12.0 | 1.12.0 | 0.7.3 | 1.12.0 |
+| AzureML-ACPT-pytorch-1.12-py39-cuda11.6-gpu | Ubuntu 20.04  | cu116 | 3.9 | 1.12.1 | 1.13.1 | 0.7.3 | 1.13.1 |
+| AzureML-ACPT-pytorch-1.12-py38-cuda11.6-gpu | Ubuntu 20.04  | cu116 | 3.8 | 1.12.1 | 1.12.0 | 0.7.3 | 1.12.0 |
 | AzureML-ACPT-pytorch-1.11-py38-cuda11.5-gpu | Ubuntu 20.04  | cu115 | 3.8 | 1.11.0 | 1.11.1 | 0.7.3 | 1.11.0 | 
 | AzureML-ACPT-pytorch-1.11-py38-cuda11.3-gpu | Ubuntu 20.04  | cu113 | 3.8 | 1.11.0 | 1.11.1 | 0.7.3 | 1.11.0 |
 

articles/synapse-analytics/sql-data-warehouse/backup-and-restore.md

@@ -20,7 +20,12 @@ Learn how to use backup and restore in Azure Synapse Dedicated SQL pool. Use ded
 
 A *data warehouse snapshot* creates a restore point you can leverage to recover or copy your data warehouse to a previous state.  Since dedicated SQL pool is a distributed system, a data warehouse snapshot consists of many files that are located in Azure storage. Snapshots capture incremental changes from the data stored in your data warehouse.
 
-A *data warehouse restore* is a new data warehouse that is created from a restore point of an existing or deleted data warehouse. Restoring your data warehouse is an essential part of any business continuity and disaster recovery strategy because it re-creates your data after accidental corruption or deletion. Data warehouse snapshot is also a powerful mechanism to create copies of your data warehouse for test or development purposes. Dedicated SQL pool restore rates can vary depending on the database size and location of the source and target data warehouse.
+A *data warehouse restore* is a new data warehouse that is created from a restore point of an existing or deleted data warehouse. Restoring your data warehouse is an essential part of any business continuity and disaster recovery strategy because it re-creates your data after accidental corruption or deletion. Data warehouse snapshot is also a powerful mechanism to create copies of your data warehouse for test or development purposes.
+
+> [!NOTE]
+> Dedicated SQL pool Recovery Time Objective (RTO) rates can vary. Factors that may affect the recovery (restore) time:
+> - The database size
+> - The location of the source and target data warehouse (i.e., geo-restore) 
 
 ## Automatic Restore Points
 

includes/front-door-edge-locations-by-abbreviation.md

@@ -13,10 +13,12 @@
 | Abbreviation | Location | Region |
 | --- | --- | --- |
 | AKL | Auckland, New Zealand | New Zealand North, Asia |
+| ASH | Ashburn, Virginia, USA | EAST US, United States |
 | ATA | Atlanta, Georgia, USA | East US, United States |
 | ATH | Athens, Greece | Greece Central, Europe |
 | BCN | Barcelona, Spain | Spain Central, Europe |
 | BER | Berlin, Germany | Germany West Central, Europe |
+| BJJ | Beijing, China | APAC |
 | BKK | Bangkok, Thailand | South East Asia |
 | BL  | Ashburn, Virginia, USA | East US, United States |
 | BN  | Boydton, Virginia, USA | East US, United States |
@@ -32,20 +34,24 @@
 | CAI | Cairo, Egypt | Africa |
 | CH  | Chicago, Illinois, USA | Central US, United States |
 | CHG | Chicago, Illinois, USA | Central US, United States |
+| CHI | Chicago, Illinois, USA | Central US, United States |
 | CPH | Copenhagen, Denmark | Denmark East, Europe |
 | CPQ | Campinas, Brazil | South Brazil, Latin America |
 | CPT | Cape Town, South Africa | South Africa North |
+| CVG | Cincinnati, Ohio, USA | US East, United States |
 | CYS | Cheyenne, Wyoming, USA | Central US, United States |
 | DAL | Dallas, Texas, USA | Central US, United States |
 | DB  | Dublin, Ireland | North Europe |
 | DEL | New Delhi, India | West India, Asia |
 | DEN | Denver, Colorado, USA | Central US, United States |
 | DFW | Dallas, Texas, USA | Central US, United States |
 | DNA | Denver, Colorado, USA | Central US, United States |
+| DOH | Doha, Qatar | Qatar Central, Qater | 
 | DUS | Duesseldorf, Germany | Germany West Central, Europe |
 | DXB | Dubai, United Arab Emirates | United Arab Emirates North, Asia |
 | EWR | Newark, New Jersey, USA | East US, United States |
 | FRA | Frankfurt, Germany | Germany West Central, Europe |
+| GRU | Sau Paulo, Brazil | Brazil South |
 | GVA | Geneva, Switzerland | Switzerland North, Europe |
 | HEL | Helsinki, Finland | West Europe |
 | HK  | Hong Kong, Hong Kong SAR | East Asia |
@@ -70,6 +76,7 @@
 | MAD | Madrid, Spain | Spain Central, Europe |
 | MAN | Manchester, United Kingdom | UK West, Europe |
 | MEL | Melbourne, Australia | Australia Southeast, Asia |
+| MEM | Memphis, Tennessee, USA | Central US, United States |
 | MEX | Queretaro, Mexico | Mexico Central |
 | MIA | Miami, Florida, USA | East US, United States |
 | MIL | Milan, Italy | Italy North, Europe |
@@ -82,11 +89,13 @@
 | NYC | New York City, New York, USA | East US, United States |
 | OSA | Osaka, Japan | Japan West, Asia |
 | OSL | Oslo, Norway | Norway East, Europe |
+| PAO | Palo Alto, California, USA | West US, United States |
 | PAR | Paris, France | France Central, Europe |
 | PDX | Portland, Oregon, USA | West US, United States |
 | PER | Perth, Australia | Australia Southeast, Asia |
 | PHL | Philadelphia, Pennsylvania, USA | East US, United States |
 | PHX | Phoenix, Arizona, USA | West US, United States |
+| PNQ | Pune, India | Central India |
 | PR  | San Juan, Puerto Rico | Latin America |
 | PRA | Saint Denis, France | France Central, Europe |
 | PRG | Prague, Czech Republic | West Europe |
@@ -97,18 +106,25 @@
 | SAN | San Diego, California, USA | West US, United States |
 | SAO | Sao Paulo, Brazil | South Brazil |
 | SCL | Santiago, Chile | Chile Central, Latin America |
+| SEL | Seoul, Singapore | Southeast Asia |
 | SG  | Singapore, Singapore | Southeast Asia |
 | SGE | Singapore, Singapore | Southeast Asia |
 | SGN | Ho Chi Minh City, Vietnam | Southeast Asia |
 | SIN | Singapore, Singapore | Southeast Asia |
 | SJC | San Jose, California, USA | West US, United States |
 | SLA | Seoul, Korea | Korea Central, Asia |
+| SLC | Salt Lake City, Utah, USA | West US, United States | 
 | SN  | San Antonio, Texas, USA | Central US, United States |
 | SOF | Sofia, Bulgaria | West Europe |
+| STB | Seattle, Washington, USA | West US, United States | 
 | STO | Stockholm, Sweden | West Europe |
 | SYD | Sydney, Australia | Australia East |
+| TEB | Secaucus, New Jersey, United States | East US, United States |
 | TLV | Tel Aviv, Israel | Israel Central, Asia |
+| TPA | Tampa, Florida, USA | East US 2, United States | 
 | TPE | Taipei, Taiwan | Taiwan North, Asia |
+| TYA | Tokyo, Japan | Japan East, Asia |
+| TYB | Tokyo, Japan | Japan East, Asia |
 | TYO | Tokyo, Japan | Japan East, Asia |
 | VIE | Vienna, Austria | Austria East, Europe |
 | WAW | Warsaw, Poland | Poland Central, Europe |

includes/virtual-network-multiple-ip-addresses-os-config.md

@@ -113,7 +113,18 @@ ping -S 10.1.0.5 outlook.com
 
 </details>
 
-### Linux (Ubuntu 14/16)
+### SUSE Linux Enterprise and openSUSE
+ 
+<details>
+  <summary>Expand</summary>
+ 
+SUSE-based distributions use the <code>cloud-netconfig</code> plugin from the <code>cloud-netconfig-azure</code> package to manage additional IP addresses. No manual configuration is required on the part of the administrator. The first IP address of an interface set on the platform is assigned via DHCP. The cloud-netconfig plugin then probes the Azure Instance Metadata Service API continuously (once per minute) for additional IP addresses assigned to the interface and adds/removes them as secondary IP addresses automatically.
+
+This plugin should be installed and enabled on new images by default.  Configuration steps for old workloads can be found here: https://www.suse.com/c/multi-nic-cloud-netconfig-ec2-azure/.
+
+</details>
+
+### Ubuntu 14/16
 
 <details>
   <summary>Expand</summary>
@@ -234,7 +245,7 @@ ip route add default via 10.1.0.1 dev eth2 table custom
 
 </details>
 
-### Linux (Ubuntu 18.04+)
+### Ubuntu 18.04+
 
 <details>
   <summary>Expand</summary>
@@ -349,7 +360,7 @@ ip route add default via 10.1.0.1 dev eth2 table custom
 
 </details>
 
-### Linux (Red Hat, CentOS, and others)
+### Red Hat Enterprise Linux, CentOS, and others
 
 <details>
   <summary>Expand</summary>
@@ -605,4 +616,4 @@ ip route add default via 10.1.0.1 dev eth2 table custom
   
   - **eth2** to the name of your secondary NIC
 
-</details>
+</details>