Retirement: Deprecation of Custom Resource Providers

In 2026, Azure Resource Manager will be deprecating the Custom Resource Provider (CuRP) service. We will retire the feature by October 31, 2026\. We will be performing a scream test on October 27, 2025, as part of this deprecation. On July 31, 2026, creates, updates, patches, and actions to custom resources and resource providers will be blocked. You will only be able to read and delete your custom resources and resource providers. We understand that this deprecation may be an inconvenience to you and your team. Here are some potential CuRP alternatives you can use to support your existing workflows. If your CuRP scenario: * Only involves triggering an endpoint without the need for persistent resource management, consider [Deployment Scripts](https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/deployment-script-template). * Only involves triggering an endpoint without the need for persistent resource management, and you use Bicep, consider [Bicep Extensions](https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/bicep-extension). * Involves triggering several different endpoints or services for your solution, consider [Azure Functions](https://learn.microsoft.com/en-us/azure/azure-functions/functions-overview). If you have any questions, please ask your Microsoft account manager to email curpdeprecation@microsoft.com with your name, company name, email contact, and subscription ID.