Skip to content
This repository has been archived by the owner on Mar 29, 2023. It is now read-only.

Azure Functions Proxies is retiring on September 30th, 2025 #292

Open
azure-deprecation-automation opened this issue Dec 5, 2022 · 1 comment
Labels
area:service-runtime All issues related to notices that are applicable to service runtimes cloud:public All issues related to Azure public cloud impact:migration-required All issues where a migration is required services:functions verified All notices that are verified by an official communication
Milestone

Comments

@azure-deprecation-automation

Azure Functions Proxies is retiring on September 30th, 2025

Deprecation ID: c8be108d-9dfe-46ba-96c8-e2afd7823781
Deadline: Sep 30, 2025
Impacted Services:

  • Azure Functions

More information:

Notice

Here's the official report from Microsoft:

Azure API Management is Microsoft’s solution to securely create and manage modern APIs at scale. It also provides advanced tools for building and maintaining APIs such as OpenAPI integration, rate limiting and exhaustive policy support.

Azure Functions Proxies are a very limited subset of these capabilities that will no longer be invested in to avoid duplication of functionality. Azure Functions Proxies will continue to remain in maintenance mode until 30 September 2025 after which they will no longer be supported.

To enable seamless upgrade of Function applications to runtime V4.x, we will be adding Proxy support back in Functions runtime V4.x by October 2022. However, migrating away from Proxies is strongly recommended.

Timeline

Phase Date Description
Announcement Dec 02, 2022 Deprecation was announced
Deprecation Sep 30, 2025 Offering will no longer be available.

Impact

Azure Functions Proxies is retiring on September 30th, 2025 and migration to Azure API Management is required.

Required Action

A migration guide is provided here.

Customers can create issues on this GitHub repo and tag them with proxy-deprecation in case of problems.

Here's the official report from Microsoft:

Please review the migration guidance and transition to Azure API Management as soon as possible to be on the recommended and long term supported path.

Contact

You can get in touch through the following options:

  • Contact Azure support (link).
  • Get answers from Microsoft Q&A (link).
@azure-deprecation-automation azure-deprecation-automation added area:service-runtime All issues related to notices that are applicable to service runtimes cloud:public All issues related to Azure public cloud impact:migration-required All issues where a migration is required services:functions verified All notices that are verified by an official communication labels Dec 5, 2022
@azure-deprecation-automation azure-deprecation-automation added this to the 2025 milestone Dec 5, 2022
@azure-deprecation-automation
Copy link
Author

This issue is automatically managed and suggest to use GitHub Discussions to discuss this deprecation.

@azure-deprecation azure-deprecation locked and limited conversation to collaborators Dec 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area:service-runtime All issues related to notices that are applicable to service runtimes cloud:public All issues related to Azure public cloud impact:migration-required All issues where a migration is required services:functions verified All notices that are verified by an official communication
Projects
None yet
Development

No branches or pull requests

1 participant