We are investigating an issue in our Business Central staging/sandbox environment where custom extensions were removed or became unavailable after a recent change/update event.
Our support partner has advised that this was caused by Microsoft updates. However, we want to confirm whether this is expected behaviour, or whether it could indicate a code deployment, extension uninstall/redeploy, environment refresh, or another change-management action.
From what we understand, extension removal can depend on how the extension was deployed, for example DEV extension vs Per-Tenant Extension, and whether the environment was updated, restored, reset, or had an extension lifecycle action performed.
We think the MSP is making code changes without us knowing which has caused the functionality to vanish. I have pushed all updates to January 31st, so this shouldn't be updating.
Any ideas would be great

Report
All responses (
Answers (