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
Copy file name to clipboardExpand all lines: articles/api-center/manage-apis-azure-cli.md
+18-4Lines changed: 18 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,10 +39,6 @@ az apic api create --resource-group myResourceGroup \
39
39
--title "Petstore API" --type "rest"
40
40
```
41
41
42
-
> [!NOTE]
43
-
> After creating an API, you can update the API's properties by using the [az apic api update](/cli/azure/apic/api#az_apic_api_update) command.
44
-
45
-
46
42
### Create an API version
47
43
48
44
Use the [az apic api version create](/cli/azure/apic/api/version#az_apic_api_version_create) command to create a version for your API.
@@ -117,8 +113,26 @@ az apic api register --resource-group myResourceGroup \
117
113
* By default, the command sets the API's **Lifecycle stage** to *design*.
118
114
* It creates an API version named according to the `version` property in the API definition (or *1-0-0* by default), and an API definition named according to the specification format (for example, *openapi*).
119
115
116
+
## Update API properties
117
+
120
118
After registering an API, you can update the API's properties by using the [az apic api update](/cli/azure/apic/api#az_apic_api_update), [az apic api version update](/cli/azure/apic/api/version#az_apic_api_version_update), and [az apic api definition update](/cli/azure/apic/api/definition#az_apic_api_definition_update) commands.
121
119
120
+
The following example updates the title of the *petstore-api* API to *Petstore API v2*.
121
+
122
+
```azurecli-interactive
123
+
az apic api update --resource-group myResourceGroup \
Use the [az apic api delete](/cli/azure/apic/api#az_apic_api_delete) command to delete an API and all of its version and definition resources. For example:
Copy file name to clipboardExpand all lines: articles/application-gateway/configuration-infrastructure.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -235,6 +235,22 @@ To use the route table to allow kubenet to work:
235
235
236
236
Any scenario where 0.0.0.0/0 needs to be redirected through a virtual appliance, a hub/spoke virtual network, or on-premises (forced tunneling) isn't supported for v2.
237
237
238
+
## Additional services
239
+
240
+
To view roles and permissions for other services, see the following links:
Copy file name to clipboardExpand all lines: articles/azure-maps/rest-api-azure-maps.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ The most recent stable release of the Azure Maps services.
34
34
35
35
## Previous releases
36
36
37
-
There are previous stable releases of an Azure Maps services that are still in use. The services in these lists will generally have a more recent version available, and are slated for retirement. If using a previous release, update to the latest version before it's retired to avoid disruption of service.
37
+
There are previous stable releases of an Azure Maps service that are still in use. The services in these lists will generally have a more recent version available, and are slated for retirement. If using a previous release, update to the latest version before it's retired to avoid disruption of service.
38
38
39
39
### Version 2022-08-01
40
40
@@ -55,7 +55,7 @@ Prerelease version of an Azure Maps service. Preview releases contain new functi
55
55
56
56
| API | API version | Description |
57
57
|-----|-------------|-------------|
58
-
|[Route][Route-2023-10-01-preview]|2023-10-01-preview | Returns the ideal route in GeoJSON between locations for multiple modes of transportation.<BR><BR>Some of the updates in this version of the Route service include:<ul><li>Routes with "via" waypoints that the route must pass through.</li><li>More geographies</li><li>More languages available for localized travel instructions.</li></ul> |
58
+
|[Route][Route-2024-07-01-preview]|2024-07-01-preview | Returns the ideal route in GeoJSON between locations for multiple modes of transportation.<BR><BR>Some of the updates in this version of the Route service include:<ul><li>New Snap to Roads API that snaps GPS data to road aligned coordinates.</li><li>Support for up to 50,000 cells in Route Matrix async.</li><li>High-definition route range polygon.</li><li>Routes with "via" waypoints that the route must pass through.</li><li>More geographies</li><li>More languages available for localized travel instructions.</li> |
59
59
60
60
<!--- Links to latest versions of each service ---------------------------------->
61
61
[Data Registry]: /rest/api/maps/data-registry
@@ -74,6 +74,6 @@ Prerelease version of an Azure Maps service. Preview releases contain new functi
|View all Azure subscriptions for the billing profile|✔|✔|✔|✔|✔|✔|✔|
147
-
|Create new Azure subscriptions|✔|✔|✘|✘|✔|✔|✘|
148
-
|Cancel Azure subscriptions|✘|✘|✘|✘|✘|✘|✘|
147
+
|Create new Azure subscriptions|✔|✔|✘|✔|✔|✔|✘|
148
+
|Cancel Azure subscriptions|✘|✘|✘|✔¹|✘|✘|✘|
149
149
|Change billing profile for the Azure subscriptions|✔|✔|✘|✘|✔|✔|✘|
150
150
151
+
¹ Invoice manager can only cancel the subscriptions they created.
152
+
151
153
## Invoice section roles and tasks
152
154
153
155
Each billing profile contains one invoice section by default. You can create more invoice sections to group cost on the billing profile's invoice. Users with roles on an invoice section can control who creates Azure subscriptions and make other purchases. Assign these roles to users who set up Azure environment for teams in our organization like engineering leads and technical architects. For more information, see [Understand invoice section](../understand/mca-overview.md#invoice-sections).
Copy file name to clipboardExpand all lines: articles/data-factory/data-movement-security-considerations.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -133,27 +133,27 @@ By default, when remote access from intranet is enabled, PowerShell uses port 80
133
133
134
134
All data transfers are via secure channel HTTPS and TLS over TCP to prevent man-in-the-middle attacks during communication with Azure services.
135
135
136
-
You can also use [IPSec VPN](../vpn-gateway/vpn-gateway-about-vpn-devices.md) or [Azure ExpressRoute](../expressroute/expressroute-introduction.md) to further secure the communication channel between your on-premises network and Azure.
136
+
You can also use [IPsec VPN](../vpn-gateway/vpn-gateway-about-vpn-devices.md) or [Azure ExpressRoute](../expressroute/expressroute-introduction.md) to further secure the communication channel between your on-premises network and Azure.
137
137
138
-
Azure Virtual Network is a logical representation of your network in the cloud. You can connect an on-premises network to your virtual network by setting up IPSec VPN (site-to-site) or ExpressRoute (private peering).
138
+
Azure Virtual Network is a logical representation of your network in the cloud. You can connect an on-premises network to your virtual network by setting up IPsec VPN (site-to-site) or ExpressRoute (private peering).
139
139
140
140
The following table summarizes the network and self-hosted integration runtime configuration recommendations based on different combinations of source and destination locations for hybrid data movement.
| On-premises | Virtual machines and cloud services deployed in virtual networks |IPSec VPN (point-to-site or site-to-site) | The self-hosted integration runtime should be installed on an Azure virtual machine in the virtual network. |
144
+
| On-premises | Virtual machines and cloud services deployed in virtual networks |IPsec VPN (point-to-site or site-to-site) | The self-hosted integration runtime should be installed on an Azure virtual machine in the virtual network. |
145
145
| On-premises | Virtual machines and cloud services deployed in virtual networks | ExpressRoute (private peering) | The self-hosted integration runtime should be installed on an Azure virtual machine in the virtual network. |
146
146
| On-premises | Azure-based services that have a public endpoint | ExpressRoute (Microsoft peering) | The self-hosted integration runtime can be installed on-premises or on an Azure virtual machine. |
147
147
148
-
The following images show the use of self-hosted integration runtime for moving data between an on-premises database and Azure services by using ExpressRoute and IPSec VPN (with Azure Virtual Network):
148
+
The following images show the use of self-hosted integration runtime for moving data between an on-premises database and Azure services by using ExpressRoute and IPsec VPN (with Azure Virtual Network):
149
149
150
150
#### Express Route
151
151
152
152
:::image type="content" source="media/data-movement-security-considerations/express-route-for-gateway.png" alt-text="Use ExpressRoute with gateway":::
153
153
154
-
#### IPSec VPN
154
+
#### IPsec VPN
155
155
156
-
:::image type="content" source="media/data-movement-security-considerations/ipsec-vpn-for-gateway.png" alt-text="IPSec VPN with gateway":::
156
+
:::image type="content" source="media/data-movement-security-considerations/ipsec-vpn-for-gateway.png" alt-text="IPsec VPN with gateway":::
157
157
158
158
### Firewall configurations and allow list setting up for IP addresses
For more information, see [Azure permissions for Networking](../role-based-access-control/permissions/networking.md) and [Virtual network permissions](../virtual-network/virtual-network-manage-subnet.md#permissions).
49
50
@@ -56,6 +57,22 @@ These scopes are structured in a parent-child relationship, with each level of h
56
57
For example, a role assigned at the subscription level can cascade down to all resources within that subscription, while a role assigned at the resource group level will only apply to resources within that specific group. Learn more about scope level
57
58
For more information, see [Scope levels](../role-based-access-control/scope-overview.md#scope-levels).
58
59
60
+
## Additional services
61
+
62
+
To view roles and permissions for other services, see the following links:
Copy file name to clipboardExpand all lines: articles/frontdoor/troubleshoot-issues.md
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -168,6 +168,20 @@ Azure Front Door users the origin host name as the SNI header during SSL handsha
168
168
169
169
Change the origin from an IP address to an FQDN to which a valid certificate is issued that matches the origin certificate.
170
170
171
+
## 429 responses from Azure Front Door
172
+
173
+
### Symptom
174
+
175
+
* A percentage of requests start showing errors with the response 429: Too many requests.
176
+
177
+
### Cause
178
+
179
+
* Azure Front Door has default platform rate limits. If your traffic exceeds the limit, AFD will start rate limiting the traffic and return 429 responses.
180
+
181
+
### Troubleshooting steps
182
+
183
+
* If you start seeing 429s for your legitimate traffic and a higher quota limited is need, create an [Azure support request](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest).
184
+
171
185
## Next steps
172
186
173
187
* Learn how to [create a Front Door](quickstart-create-front-door.md).
0 commit comments