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
Copy file name to clipboardExpand all lines: articles/cdn/edgio-retirement-faq.md
+63-18Lines changed: 63 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,58 +6,103 @@ services: cdn
6
6
author: duongau
7
7
ms.service: azure-cdn
8
8
ms.topic: how-to
9
-
ms.date: 12/17/2024
9
+
ms.date: 12/20/2024
10
10
ms.author: duau
11
11
---
12
12
13
13
# Azure CDN from Edgio retirement FAQ
14
14
15
-
Azure CDN from Edgio will be retired on January 15, 2025. You must migrate your workload to Azure Front Door before this date to avoid service disruption. This article provides answers to common questions about the retirement of Azure CDN from Edgio.
15
+
Azure CDN from Edgio will be shut down on January 15, 2025. You must migrate your workload to Azure Front Door before January 7, 2025 to avoid service disruption. This article provides answers to common questions about the retirement of Azure CDN from Edgio.
16
16
17
17
## Frequently asked questions
18
18
19
19
### Why was the retirement date of Azure CDN from Edgio changed from November 4, 2025, to January 15, 2025?
20
20
21
-
Edgio has informed us that their platform is now scheduled to shut down on January 15, 2025. Therefore, all Azure CDN from Edgio customers must migrate their workloads to Azure Front Door or other CDN services before this date.
21
+
[Akamai acquired select assets](https://www.prnewswire.com/news-releases/akamai-completes-acquisition-of-select-assets-of-edgio-302331398.html) from Edgio in December of 2024, and Microsoft was informed that the Edgio platform will end service on January 15, 2025. All Azure CDN from Edgio users must migrate their workloads to Azure Front Door or other CDN services before this date.
22
22
23
23
### I see Edgio filed for Chapter 11 bankruptcy. Can Microsoft guarantee that Azure CDN from Edgio’s availability and services until November 4, 2025?
24
24
25
-
Edgio informed us that their services remain operational until at least January 15, 2025. However, we can't guarantee that Edgio doesn't unexpectedly cease operations before this date due to circumstances beyond our control.
25
+
Edgio has informed us that their services will remain operational until at least January 15, 2025. However, we can't guarantee that Edgio won't unexpectedly cease operations before this date due to circumstances beyond our control. Therefore, we'll automatically migrate your workload if you haven't taken action by January 7, 2025.
26
26
27
-
### What options do I have with migrating my workloads from Azure CDN from Edgio?
27
+
### How can I see my impacted Azure CDN from Edgio resources?
28
28
29
-
You're encouraged to migrate your workloads to Microsoft's flagship CDN product called Azure Front Door Standard or Premium. Next steps:
30
-
1. Review [Azure Front Door and Azure CDN features](../frontdoor/front-door-cdn-comparison.md) to determine if Azure Front Door is compatible with your workload(s).
31
-
2. Understand [Azure Front Door Pricing](https://azure.microsoft.com/pricing/details/frontdoor/).
32
-
3. Follow the [Azure CDN to Azure Front Door migration guide](../frontdoor/migrate-cdn-to-front-door.md). This guide provides detailed instructions on how to set up an Azure Front Door profile, test functionality, and migrate your compatible workloads from Azure CDN from Edgio to Azure Front Door with the help of Azure Traffic Manager.
29
+
You can see them in the [Migrate away from Azure CDN from Edgio](https://www.portal.azure.com/#view/Microsoft_Azure_Expert/RecommendationList.ReactView/recommendationTypeId/2c9e3f2a-7373-45e1-ab8b-f361e5f0c37f) dashboard.
30
+
31
+
### What options do I have with migrating my workloads out of Azure CDN from Edgio?
32
+
33
+
The following is a recap of the migration options we sent to all users:
34
+
35
+
- Validate if your workloads on Azure CDN from Edgio are compatible with Azure Front Door (see here and here to help verify) and migrate as soon as possible using these instructions before January 7, 2025.
36
+
37
+
- If Azure Front Door isn't compatible with your workloads, determine if Akamai could be compatible via Azure Marketplace or work with another CDN provider. If you chose to work with Akamai, feel free to contact Microsoft Support, and we can put you in touch with the Akamai team dedicated to performing migrations to their platform.
38
+
39
+
> [!IMPORTANT]
40
+
> - If you plan a migration to Akamai or another CDN provider, you will need set a Feature Flag by following these instructions (select the Feature Flag “DoNotForceMigrateEdgioCDNProfiles”) before January 7, 2025. Doing so will prevent Microsoft from migrating you to Azure Front Door (please see below). Note you will have until January 14, 2025 to complete your migration to another CDN, but again Microsoft cannot guarantee your services will be available on the Edgio platform before this date.
41
+
> - The Azure Marketplace is currently not available for customers in South Korea.
42
+
> - Please be advised we will need to halt all configuration changes to Azure CDN by Edgio profiles starting on January 3, 2025. This means you will not be able update your CDN profile configuration, but your services on Azure CDN from Edgio will still operate until you are migrated or the Edgio platform is shut down on January 15, 2025
43
+
44
+
- If you have any services running on Azure CDN from Edgio on January 7, 2025 and haven't informed us of your plans (please see above), we'll attempt to migrate your services over to Azure Front Door on January 7, 2025. We'll be performing this migration to Azure Front Door on a “best effort” basis, and doing so might cause issues related to the billing, features, availability, and/or performance you're currently consuming with Azure CDN from Edgio.
45
+
46
+
### What are some key things I should do to verify my workloads are working properly on AFD?
33
47
34
-
### If I determine my workload isn't a match for Azure Front Door, what are my options?
48
+
- Look at [metrics and logs](../frontdoor/front-door-diagnostics.md) for Azure Front Door resources to observe for 4xx/5xx errors, cache/byte hit ratios, and origin health.
49
+
- See the following troubleshooting guides for any other issues:
50
+
-[Troubleshoot Azure Front Door common issues](../frontdoor/troubleshoot-issues.md)
51
+
-[Troubleshoot general performance problems](../frontdoor/troubleshoot-performance-issues.md)
Consider whether Akamai or another CDN provider might be compatible with your needs. You can explore Akamai options through Azure Marketplace. If you decide to work with Akamai, contact Microsoft Support for assistance, and we can connect you with the Akamai team dedicated to migrations.
54
+
### How does Azure Front Door billing work?
37
55
38
-
> [!NOTE]
39
-
> The Azure Marketplace is currently unavailable for customers in South Korea.
56
+
Depending on your workloads, Azure Front Door can be more cost-effective than Azure CDN from Edgio. Note that the Azure Front Door billing model differs from Azure CDN from Edgio and includes different billing components. Specifically, Azure Front Door charges a base fee for each profile deployed. Additionally, charges are incurred for requests and data transfer based on usage. See the following for details:
40
57
41
-
### If I determined my workload isn't a match for Azure Front Door, what are my options?
58
+
-[Understand Azure Front Door billing](../frontdoor/billing.md)
If you find that Azure Front Door isn't suitable for your workload, we offer an alternative service called [Routing Preference Unmetered](../virtual-network/ip-services/routing-preference-unmetered.md), also known as "CDN Interconnect." This service might allow free data transfer for traffic egressing from your Azure resources to another CDN of your choice.
63
+
For any questions regarding billing changes, reach out to our support team or your account team.
64
+
65
+
### What options do I have with migrating my workloads from Azure CDN from Edgio?
66
+
67
+
You're encouraged to migrate your workloads to Microsoft's flagship CDN product called Azure Front Door Standard or Premium. Next steps:
68
+
1. Review [Azure Front Door and Azure CDN features](../frontdoor/front-door-cdn-comparison.md) to determine if Azure Front Door is compatible with your workloads.
69
+
2. Understand [Azure Front Door Pricing](https://azure.microsoft.com/pricing/details/frontdoor/).
70
+
3. Follow the [Azure CDN to Azure Front Door migration guide](../frontdoor/migrate-cdn-to-front-door.md). This guide provides detailed instructions on how to set up an Azure Front Door profile, test functionality, and migrate your compatible workloads from Azure CDN from Edgio to Azure Front Door with the help of Azure Traffic Manager.
44
71
45
72
### Does Microsoft validate my workloads work on Azure Front Door?
46
73
47
-
You need to determine if Azure Front Door suits your workloads. We recommend setting up a test environment to validate that your services are compatible with Azure Front Door.
74
+
No, you need to determine if Azure Front Door suits your workloads. We recommend setting up a test environment to validate that your services are compatible with Azure Front Door.
48
75
49
76
### What will happen if I don't take action before January 15, 2025?
50
77
51
78
If no action is taken before January 15, 2025, Azure CDN from Edgio profiles and associated data will be removed from Edgio systems. It's imperative that users migrate their workloads before this date to avoid any service disruptions and data loss.
52
79
80
+
### What will happen after Microsoft migrates my workloads to Azure Front Door on January 7, 2025?
81
+
82
+
After the migration, you'll receive an email notification confirming whether your workloads have been successfully migrated to Azure Front Door Standard or if the migration was unsuccessful. We're migrating you to Azure Front Door Standard as it may be more cost-effective. If you need the extra features of Azure Front Door Premium, you can [upgrade your service](../frontdoor/tier-upgrade.md).
83
+
84
+
If the migration was unsuccessful or if you encounter issues with availability, performance, or feature functionality after a successful migration, contact Microsoft support for assistance.
85
+
53
86
### How is Microsoft communicating the retirement of Azure CDN from Edgio, and how often are reminders sent?
54
87
55
88
We communicate the retirement of Azure CDN from Edgio through multiple channels, including email notifications and in-portal messages. Reminders are sent at least monthly to all users with active Edgio profiles to ensure they're aware of the upcoming changes and necessary actions.
56
89
57
-
### When will it no longer be possible to create new Azure CDN from Edgio profiles?
90
+
### What is the recap of the key dates?
58
91
59
-
New Azure CDN from Edgio profiles can't be created after December 13, 2024.
| December 13, 2024 | Creation of new Azure CDN from Edgio profiles is no longer allowed. |
95
+
| January 3, 2025 | No further changes to Azure CDN from Edgio profiles will be permitted. |
96
+
| January 6, 2025 | Deadline for setting a Feature Flag to prevent automatic migration to Azure Front Door. |
97
+
| January 7, 2025 | Automatic migration of remaining Azure CDN from Edgio profiles to Azure Front Door begins if the Feature Flag isn't set. |
98
+
| January 7-8, 2025 | Notifications sent to customers regarding the status of their migration to Azure Front Door. |
99
+
| January 14, 2025 | Final day of service for Azure CDN from Edgio. |
100
+
| January 15, 2025 | Shutdown of the Edgio platform. |
60
101
61
102
### Can I request an extension for the retirement/shutdown of the Azure CDN from Edgio service?
62
103
63
104
No, extensions aren't possible. Edgio confirmed that their platform will shut down by January 15, 2025.
105
+
106
+
### Can I retain my existing *.azureedge.net domain when I move to Azure Front Door?
107
+
108
+
You can temporarily retain your *.azureedge.net domain by following the instructions provided in [Migrate to Azure Front Door while retaining *.azureedge.net domain](migrate-cdn-to-front-door-retain-edge-domain.md). However, this is only a short-term solution due to the urgent retirement of Azure CDN from Edgio. Relying on domains like *.azureedge.net and *.azurefd.net isn't recommended as it poses availability risks. To ensure greater flexibility and avoid a single point of failure, it's advisable to adopt a custom domain as soon as possible.
0 commit comments