Dynamics 365 Year-End Change Freeze: What to Lock Before December
A year-end freeze that only blocks your own team's changes misses two risks: Microsoft updates that keep landing in December, and credentials, licences and jobs that expire over the break. What to lock and plan: Name
A year-end freeze that only blocks your own team's changes misses two risks: Microsoft updates that keep landing in December, and credentials, licences and jobs that expire over the break.
What to lock and plan:
- Name the update version you are protecting, and either take the next update early or pause and take it after the freeze
- Set up 1 January changes in advance, such as tax rates with start dates
- Keep the December ledger period on hold rather than closed, because closed cannot be reversed
- Inventory everything expiring before the end of January, give each item an owner and renew before 1 December
- Define an emergency change route with at least two named approvers
Read the full guide: https://www.dynamicsmonk.com/blog/dynamics-365-year-end-change-freeze
📰 Read the original article on Dev.to Security
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.