Skip to content

Commit 0b98f42

Browse files
TaojunshenTaojunshen
authored
Merge pull request #261981 from MicrosoftDocs/main
12/27/2023 AM Publish
2 parents c8dba18 + ed1fa13 commit 0b98f42

File tree

8 files changed

+132
-126
lines changed

8 files changed

+132
-126
lines changed

‎articles/app-service/configure-language-java.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ With the [Maven Plugin for Azure Web Apps](https://github.com/microsoft/azure-ma
6666
mvn com.microsoft.azure:azure-webapp-maven-plugin:2.11.0:config
6767
```
6868

69-
This command adds a `azure-webapp-maven-plugin` plugin and related configuration by prompting you to select an existing Azure Web App or create a new one. Then you can deploy your Java app to Azure using the following command:
69+
This command adds an `azure-webapp-maven-plugin` plugin and related configuration by prompting you to select an existing Azure Web App or create a new one. Then you can deploy your Java app to Azure using the following command:
7070

7171
```shell
7272
mvn package azure-webapp:deploy

‎articles/communication-services/quickstarts/email/add-custom-verified-domains.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -204,7 +204,7 @@ The following links provide additional information on how to add a CNAME record
204204

205205
## Next steps
206206

207-
* [Get started by connecting Email Communication Service with a Azure Communication Service resource](../../quickstarts/email/connect-email-communication-resource.md)
207+
* [Get started by connecting Email Communication Service with an Azure Communication Service resource](../../quickstarts/email/connect-email-communication-resource.md)
208208

209209
* [How to send an email using Azure Communication Service](../../quickstarts/email/send-email.md)
210210

‎articles/communication-services/quickstarts/email/create-email-communication-resource.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ Get started with Email by provisioning your first Email Communication Services r
4444

4545
* [Email domains and sender authentication for Azure Communication Services](../../concepts/email/email-domain-and-sender-authentication.md)
4646

47-
* [Get started by connecting Email Communication Service with a Azure Communication Service resource](../../quickstarts/email/connect-email-communication-resource.md)
47+
* [Get started by connecting Email Communication Service with Azure Communication Service resource](../../quickstarts/email/connect-email-communication-resource.md)
4848

4949
The following documents may be interesting to you:
5050

‎articles/defender-for-cloud/agentless-vulnerability-assessment-aws.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ In every account where enablement of this capability is completed, all images st
1818

1919
Container vulnerability assessment powered by Microsoft Defender Vulnerability Management has the following capabilities:
2020

21-
- **Scanning OS packages** - container vulnerability assessment has the ability to scan vulnerabilities in packages installed by the OS package manager in Linux and Windows OS. See the [full list of the supported OS and their versions](support-matrix-defender-for-containers.md#registries-and-images-support-for-aws---vulnerability-assessment-powered-by-microsoft-defender-vulnerability-management).
21+
- **Scanning OS packages** - container vulnerability assessment has the ability to scan vulnerabilities in packages installed by the OS package manager in Linux and Windows operating systems. See the [full list of the supported OS and their versions](support-matrix-defender-for-containers.md#registries-and-images-support-for-aws---vulnerability-assessment-powered-by-microsoft-defender-vulnerability-management).
2222

2323
- **Language specific packages** – **Linux only** - support for language specific packages and files, and their dependencies installed or copied without the OS package manager. See the [complete list of supported languages](support-matrix-defender-for-containers.md#registries-and-images-support-for-aws---vulnerability-assessment-powered-by-microsoft-defender-vulnerability-management).
2424

@@ -40,7 +40,7 @@ Container vulnerability assessment powered by Microsoft Defender Vulnerability M
4040
The triggers for an image scan are:
4141

4242
- **One-time triggering**:
43-
- Each image pushed to a container registry is triggered to be scanned. In most cases, the scan is completed within a few hours, but sometin rare cases it might take up to 24 hors.
43+
- Each image pushed to a container registry is triggered to be scanned. In most cases, the scan is completed within a few hours, but in rare cases it might take up to 24 hours.
4444
- Each image pulled from a registry is triggered to be scanned within 24 hours.
4545

4646

‎articles/mariadb/concepts-connectivity-architecture.md

Lines changed: 58 additions & 56 deletions
Original file line numberDiff line numberDiff line change
@@ -31,62 +31,64 @@ As part of ongoing service maintenance, we'll periodically refresh compute hardw
3131
* You hard code the gateway IP addresses in the connection string of your application. It is **not recommended**. You should use fully qualified domain name (FQDN) of your server in the format `<servername>.mariadb.database.azure.com`, in the connection string for your application.
3232
* You don't update the newer gateway IP addresses in the client-side firewall to allow outbound traffic to be able to reach our new gateway rings.
3333

34+
> [!IMPORTANT]
35+
> If customer connectivity stack needs to connect directly to gateway instead of **recommended DNS name approach**, or allow-list gateway in the firewall rules for connections to\from customer infrastructure, we **strongly encourage** customers to use Gateway IP address **subnets** versus hardcoding static IP in order to not be impacted by this activity in a region that may cause IP to change within the subnet range.
36+
3437
The following table lists the gateway IP addresses of the Azure Database for MariaDB gateway for all data regions. The most up-to-date information of the gateway IP addresses for each region is maintained in the table below. In the table below, the columns represent following:
3538

36-
* **Gateway IP addresses:** This column lists the current IP addresses of the gateways hosted on the latest generation of hardware. If you're provisioning a new server, we recommend that you open the client-side firewall to allow outbound traffic for the IP addresses listed in this column.
37-
* **Gateway IP addresses (decommissioning):** This column lists the IP addresses of the gateways hosted on an older generation of hardware that is being decommissioned right now. If you're provisioning a new server, you can ignore these IP addresses. If you have an existing server, continue to retain the outbound rule for the firewall for these IP addresses as we haven't decommissioned it yet. If you drop the firewall rules for these IP addresses, you may get connectivity errors. Instead, you're expected to proactively add the new IP addresses listed in Gateway IP addresses column to the outbound firewall rule as soon as you receive the notification for decommissioning. This will ensure when your server is migrated to latest gateway hardware, there's no interruptions in connectivity to your server.
38-
* **Gateway IP addresses (decommissioned):** This column lists the IP addresses of the gateway rings, which are decommissioned and are no longer in operations. You can safely remove these IP addresses from your outbound firewall rule.
39-
40-
| **Region name** | **Gateway IP addresses** |**Gateway IP addresses (decommissioning)** | **Gateway IP addresses (decommissioned)** |
41-
|:----------------|:-------------------------|:-------------------------------------------|:------------------------------------------|
42-
| Australia Central| 20.36.105.0 | | |
43-
| Australia Central2 | 20.36.113.0 | | |
44-
| Australia East | 40.79.161.1, 13.70.112.32 | 13.75.149.87 | |
45-
| Australia South East |13.77.49.33, 191.239.192.109 | 13.73.109.251 | |
46-
| Brazil South |191.233.201.8, 191.233.200.16 | | 104.41.11.5|
47-
| Canada Central |40.85.224.249 | | |
48-
| Canada East | 40.69.105.32 |40.86.226.166 | |
49-
| Central US | 23.99.160.139, 52.182.136.37, 52.182.136.38 | 13.67.215.62 | |
50-
| China East | 139.219.130.35 | | |
51-
| China East 2 | 40.73.82.1 | | |
52-
| China North | 139.219.15.17 | | |
53-
| China North 2 | 40.73.50.0 | | |
54-
| East Asia | 191.234.2.139, 52.175.33.150, 13.75.33.20, 13.75.33.21 | | |
55-
| East US |40.71.8.203, 40.71.83.113 |40.121.158.30|191.238.6.43 |
56-
| East US 2 | 40.70.144.38, 52.167.105.38 | 52.177.185.181 | |
57-
| France Central | 40.79.137.0, 40.79.129.1 | | |
58-
| France South | 40.79.177.0, 40.79.176.40 | | |
59-
| Germany Central | 51.4.144.100 | | |
60-
| Germany North | 51.116.56.0 | |
61-
| Germany North East | 51.5.144.179 | | |
62-
| Germany West Central | 51.116.152.0 | |
63-
| India Central | 104.211.96.159 | | |
64-
| India South | 104.211.224.146 | | |
65-
| India West | 104.211.144.32 |104.211.160.80 | |
66-
| Japan East | 40.79.192.23, 40.79.184.8 | 13.78.61.196 | |
67-
| Japan West | 191.238.68.11, 40.74.96.6, 40.74.96.7 | 104.214.148.156 | |
68-
| Korea Central | 52.231.17.13 | 52.231.32.42 | |
69-
| Korea South | 52.231.145.3 | 52.231.200.86 | |
70-
| North Central US | 52.162.104.35, 52.162.104.36 | 23.96.178.199 | |
71-
| North Europe | 52.138.224.6, 52.138.224.7 | 40.113.93.91 |191.235.193.75 |
72-
| South Africa North | 102.133.152.0 | | |
73-
| South Africa West | 102.133.24.0 | | |
74-
| South Central US |104.214.16.39, 20.45.120.0 |13.66.62.124 |23.98.162.75 |
75-
| South East Asia | 40.78.233.2, 23.98.80.12 | 104.43.15.0 | |
76-
| Switzerland North | 51.107.56.0 ||
77-
| Switzerland West | 51.107.152.0| ||
78-
| UAE Central | 20.37.72.64 | | |
79-
| UAE North | 65.52.248.0 | | |
80-
| UK South | 51.140.184.11 | | |
81-
| UK West | 51.141.8.11 | | |
82-
| West Central US | 13.71.193.34 | 13.78.145.25| |
83-
| West Europe |13.69.105.208, 104.40.169.187 | 40.68.37.158 | 191.237.232.75 |
84-
| West US |13.86.216.212, 13.86.217.212 |104.42.238.205 | 23.99.34.75|
85-
| West US 2 | 13.66.226.202 | | |
39+
* **Region Name:** This column lists the name of Azure region where Azure Database for PostgreSQL - Single Server is offered.
40+
* **Gateway IP address subnets:** This column lists the IP address subnets of the gateway rings located in the particular region. As we retire older gateway hardware, we recommend that you open the client-side firewall to allow outbound traffic for the IP address subnets in the region you're operating.
41+
42+
| **Region name** | **Gateway IP address subnets** |
43+
|:----------------|:------------------------------------------|
44+
| Australia Central | 20.36.105.32/29 |
45+
| Australia Central 2 | 20.36.113.32/29 |
46+
| Australia East | 13.70.112.32/29, 40.79.160.32/29, 40.79.168.32/29 |
47+
| Australia South East |13.77.49.32/29 |
48+
| Brazil South | 191.233.200.32/29, 191.234.144.32/29|
49+
| Canada Central | 13.71.168.32/29, 20.38.144.32/29, 52.246.152.32/29|
50+
| Canada East | 40.69.105.32/29 |
51+
| Central US | 104.208.21.192/29, 13.89.168.192/29, 52.182.136.192/29
52+
| China East | 52.130.112.136/29|
53+
| China East 2 | 52.130.120.88/29|
54+
| China East 3 | 52.130.128.88/29|
55+
| China North | 52.130.128.88/29 |
56+
| China North 2 | 52.130.40.64/29|
57+
| China North 3 | 13.75.32.192/29, 13.75.33.192/29 |
58+
| East Asia | 13.75.32.192/29, 13.75.33.192/29|
59+
| East US |20.42.65.64/29, 20.42.73.0/29, 52.168.116.64/29|
60+
| East US 2 |104.208.150.192/29, 40.70.144.192/29, 52.167.104.192/29|
61+
| France Central | 40.79.136.32/29, 40.79.144.32/29 |
62+
| France South | 40.79.176.40/29, 40.79.177.32/29|
63+
| Germany West Central | 51.116.152.32/29, 51.116.240.32/29, 51.116.248.32/29|
64+
| India Central | 104.211.86.32/29, 20.192.96.32/29|
65+
| India South | 40.78.192.32/29, 40.78.193.32/29|
66+
| India West | 104.211.144.32/29, 104.211.145.32/29 |
67+
| Japan East | 13.78.104.32/29, 40.79.184.32/29, 40.79.192.32/29 |
68+
| Japan West | 40.74.96.32/29 |
69+
| Korea Central | 20.194.64.32/29,20.44.24.32/29, 52.231.16.32/29 |
70+
| Korea South | 52.231.145.0/29 |
71+
| North Central US | 52.162.105.192/29|
72+
| North Europe |13.69.233.136/29, 13.74.105.192/29, 52.138.229.72/29 |
73+
| South Africa North | 102.133.120.32/29, 102.133.152.32/29, 102.133.248.32/29 |
74+
| South Africa West | 102.133.25.32/29|
75+
| South Central US |20.45.121.32/29, 20.49.88.32/29, 20.49.89.32/29, 40.124.64.136/29|
76+
| South East Asia | 13.67.16.192/29, 23.98.80.192/29, 40.78.232.192/29 |
77+
| Switzerland North |51.107.56.32/29, 51.103.203.192/29, 20.208.19.192/29, 51.107.242.32/27|
78+
| Switzerland West | 51.107.153.32/29|
79+
| UAE Central | 20.37.72.96/29, 20.37.73.96/29 |
80+
| UAE North | 40.120.72.32/29, 65.52.248.32/29 |
81+
| UK South |51.105.64.32/29, 51.105.72.32/29, 51.140.144.32/29|
82+
| UK West | 51.140.208.96/29, 51.140.209.32/29 |
83+
| West Central US | 13.71.193.32/29 |
84+
| West Europe | 104.40.169.32/29, 13.69.112.168/29, 52.236.184.32/29|
85+
| West US |13.86.217.224/29|
86+
| West US 2 | 13.66.136.192/29, 40.78.240.192/29, 40.78.248.192/29|
87+
| West US 3 | 20.150.168.32/29, 20.150.176.32/29, 20.150.184.32/29 |
8688

8789
## Connection redirection
8890

89-
Azure Database for MariaDB supports another connection policy, **redirection**, that helps to reduce network latency between client applications and MariaDB servers. With this feature, after the initial TCP session is established to the Azure Database for MariaDB server, the server returns the backend address of the node hosting the MariaDB server to the client. Thereafter, all subsequent packets flow directly to the server, bypassing the gateway. As packets flow directly to the server, latency and throughput have improved performance.
91+
Azure Database for MariaDB supports another connection policy, **redirection** that helps to reduce network latency between client applications and MariaDB servers. With this feature, after the initial TCP session is established to the Azure Database for MariaDB server, the server returns the backend address of the node hosting the MariaDB server to the client. Thereafter, all subsequent packets flow directly to the server, bypassing the gateway. As packets flow directly to the server, latency and throughput have improved performance.
9092

9193
This feature is supported in Azure Database for MariaDB servers with engine versions 10.2 and 10.3.
9294

@@ -99,29 +101,29 @@ Support for redirection is available in the PHP [mysqlnd_azure](https://github.c
99101

100102
### What you need to know about this planned maintenance?
101103

102-
This is a DNS change only, which makes it transparent to clients. While the IP address for FQDN is changed in the DNS server, the local DNS cache will be refreshed within 5 minutes, and it's automatically done by the operating systems. After the local DNS refresh, all the new connections will connect to the new IP address, all existing connections will remain connected to the old IP address with no interruption until the old IP addresses are fully decommissioned. The old IP address will roughly take three to four weeks before getting decommissioned; therefore, it should have no effect on the client applications.
104+
This is a DNS change only, which makes it transparent to clients. While the IP address for FQDN is changed in the DNS server, the local DNS cache is refreshed within 5 minutes, and it's automatically done by the operating systems. After the local DNS refresh, all the new connections will connect to the new IP address, all existing connections will remain connected to the old IP address with no interruption until the old IP addresses are fully decommissioned. The old IP address will roughly take three to four weeks before getting decommissioned; therefore, it should have no effect on the client applications.
103105

104106
### What are we decommissioning?
105107

106-
Only Gateway nodes will be decommissioned. When users connect to their servers, the first stop of the connection is to gateway node, before connection is forwarded to server. We're decommissioning old gateway rings (not tenant rings where the server is running) refer to the [connectivity architecture](#connectivity-architecture) for more clarification.
108+
Only Gateway nodes are decommissioned. When users connect to their servers, the first stop of the connection is to gateway node, before connection is forwarded to server. We're decommissioning old gateway rings (not tenant rings where the server is running) refer to the [connectivity architecture](#connectivity-architecture) for more clarification.
107109

108110
### How can you validate if your connections are going to old gateway nodes or new gateway nodes?
109111

110-
Ping your server's FQDN, for example ``ping xxx.mariadb.database.azure.com``. If the returned IP address is one of the IPs listed under Gateway IP addresses (decommissioning) in the document above, it means your connection is going through the old gateway. Contrarily, if the returned Ip address is one of the IPs listed under Gateway IP addresses, it means your connection is going through the new gateway.
112+
Ping your server's FQDN, for example ``ping xxx.mariadb.database.azure.com``. If the returned IP address is one of the IPs listed under Gateway IP addresses (decommissioning) in the document above, it means your connection is going through the old gateway. Contrarily, if the returned Ip-address is one of the IPs listed under Gateway IP addresses, it means your connection is going through the new gateway.
111113

112114
You may also test by [PSPing](/sysinternals/downloads/psping) or TCPPing the database server from your client application with port 3306 and ensure that return IP address isn't one of the decommissioning IP addresses
113115

114116
### How do I know when the maintenance is over and will I get another notification when old IP addresses are decommissioned?
115117

116-
You'll receive an email to inform you when we'll start the maintenance work. The maintenance can take up to one month depending on the number of servers we need to migrate in al regions. Prepare your client to connect to the database server using the FQDN or using the new IP address from the table above.
118+
You receive an email to inform you when we start the maintenance work. The maintenance can take up to one month depending on the number of servers we need to migrate in al regions. Prepare your client to connect to the database server using the FQDN or using the new IP address from the table above.
117119

118120
### What do I do if my client applications are still connecting to old gateway server?
119121

120122
This indicates that your applications connect to server using static IP address instead of FQDN. Review connection strings and connection pooling setting, AKS setting, or even in the source code.
121123

122124
### Is there any impact for my application connections?
123125

124-
This maintenance is just a DNS change, so it's transparent to the client. Once the DNS cache is refreshed in the client (automatically done by operation system), all the new connection will connect to the new IP address and all the existing connection will still working fine until the old IP address fully get decommissioned, which several weeks later. And the retry logic isn't required for this case, but it's good to see the application have retry logic configured. Either use FQDN to connect to the database server or enable list the new 'Gateway IP addresses' in your application connection string.
126+
This maintenance is just a DNS change, so it's transparent to the client. Once the DNS cache is refreshed in the client (automatically done by operation system), all the new connections connect to the new IP address and all the existing connections will still work fine until the old IP address is fully decommissioned, which happens several weeks later. And the retry logic isn't required for this case, but it's good to see the application have retry logic configured. Either use FQDN to connect to the database server or enable list the new 'Gateway IP addresses' in your application connection string.
125127
This maintenance operation won't drop the existing connections. It only makes the new connection requests go to new gateway ring.
126128

127129
### Can I request for a specific time window for the maintenance?

0 commit comments

Comments
 (0)