Azure App Configuration's offline caching in SDK is retiring

[azure-deprecation-automation]

Azure App Configuration's offline caching in SDK is retiring

Deadline: Jan 01, 2023 Impacted Services:

• Azure App Configuration

More information:

• https://github.com/Azure/AppConfiguration-Announcements/issues/20
• https://docs.microsoft.com/en-us/azure/azure-app-configuration/concept-disaster-recovery?tabs=core2x#high-availability-architecture

Notice

This means that your application will have a higher dependency as it no longer caches things

Here's the official report from Microsoft:

We recently revisited the problems we were trying to solve with offline caching since this library was launched in 2019. We found that OfflineCache was being used as a fallback configuration source in case the App Configuration service is down. However, storing configuration data in a local environment outside your App Configuration store can potentially lead to issues. These include difficulties enforcing data access policies and retaining sensitive information in unreliable environments. In the last two years since we went to GA, we have invested heavily in server- side resiliency and availability. Please check our recommendation for highly available App Configuration.

Timeline

Phase	Date	Description
Announcement	Dec 17, 2021	Deprecation was announced
Deprecation	Jan 01, 2023	This is a placeholder for deprecation as the end date is not known yet.

Impact

Azure App Configuration's offline caching in SDK is retiring as of v5.0 (preview) and recommend using highly available App Configuration setup.

Required Action

Here's the official report from Microsoft:

Therefore, we are deprecating all offline caching capabilities with the release of v5.0.0 preview, in favor of improving server-side reliability.

Contact

You can open an issue on GitHub.

[azure-deprecation-automation]

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