Add deprecation process documentation for legacy Function App connector migrations - #14310
Closed
Bhagya Lakshmi Kukula (Bhagya767) wants to merge 1 commit into
Closed
Add deprecation process documentation for legacy Function App connector migrations#14310Bhagya Lakshmi Kukula (Bhagya767) wants to merge 1 commit into
Bhagya Lakshmi Kukula (Bhagya767) wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a deprecation guide for ISVs migrating legacy Azure Function App data connectors to CCF/CCP. This documents the safe deprecation path to prevent accidental deletion of function app zips that are still referenced by customer deployments.
Problem
When customers deploy a function app connector, the ARM template permanently writes an aka.ms link into their Function App's
WEBSITE_RUN_FROM_PACKAGEsetting. This link points to a zip hosted in this repository. If the zip is deleted, customer function apps silently fail on cold start and log ingestion stops with no warning.This risk was identified in PR #14005, where a CCF migration PR proposed deleting legacy function app files with no grace period. The PR was closed without merging — no customer impact occurred — but there was no documented process to prevent this in future submissions.
What's included
DataConnectors/Deprecation-Guide-FunctionApp-to-CCF.md: Documents the 4-phase deprecation process (build CCF → mark deprecated → migration window → removal after aka.ms retargeting), hard rules for preserving legacy files, and PR checklists for both contributors and reviewers.