[Documentation] Clarify "Update Fabric Eventhouse" step applicability in upgrade guide #1678
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.
The upgrade guide's Step 2 previously stated that "The Microsoft Fabric eventhouse database schema must be manually updated with each release" without clarifying when this step applies, causing confusion for users who aren't using Microsoft Fabric as their primary data store.
Changes Made
Added conditional language to Step 2 that clearly indicates this step only applies when using Microsoft Fabric as a primary data store:
Impact
This change resolves user confusion by:
The change is minimal (5 lines added) and follows existing documentation patterns used in Steps 1, 4, and 5 of the same guide.
Fixes #1669.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.