Azure Custom Resource Providers to be retired Oct 2026
Azure Resource Manager will deprecate the Custom Resource Provider (CuRP) service, retiring the feature by October 31, 2026. Creates, updates, and patches to custom resources will be blocked starting July 31, 2026, allowing only reads and deletes. Alternatives like Deployment Scripts, Bicep Extensions, or Azure Functions are suggested for migrated workflows.
- →Azure Custom Resource Provider (CuRP) deprecation and retirement
- →Alternative solutions for CuRP scenarios
Deprecations (1) ›
- Azure Custom Resource Provider (CuRP) deprecation and retirement
The Custom Resource Provider (CuRP) service within Azure Resource Manager will be deprecated, with the feature scheduled for retirement by October 31, 2026. A 'scream test' is planned for October 27, 2025. From July 31, 2026, operations like creates, updates, and patches on custom resources and providers will be blocked, limiting functionality to reads and deletes.
Notes (1) ›
- Alternative solutions for CuRP scenarios
For workflows previously using CuRP, Microsoft suggests several alternatives. Deployment Scripts can be used for triggering endpoints without persistent resource management. Bicep Extensions are an option if Bicep is used for similar endpoint triggering scenarios. Azure Functions are recommended for solutions involving the triggering of multiple endpoints or services.
https://azure.microsoft.com/en-us/updates/?id=513892
Related releases
- Azure Functions: .NET 8 & 9 support ends Nov 2026; upgrade to .NET 10 Azure Updates ·
- Azure Functions: PowerShell 7.4 Support Ends November 2026 Azure Updates ·
- Azure Functions: Node.js 22 Support Ending April 30, 2027 Azure Updates ·
- Azure Functions Generally Available for PowerShell 7.6 Azure Updates ·
- Public Preview: Guided Copilot Experience for Building Azure Apps in VS Code Azure Updates ·
- Azure Foundry Agent Service Adds Routines for Automated Agent Triggers Azure Updates ·