Feedback on Validation executing domain join and future breaking changes

Start by locating the Azure Local deployment documentation referenced in the issue and review how the Validation phase and domain join are described. The issue names no repository files or tests; done means the documentation clearly warns about configuration changes and the requested breaking-change communication guidance is addressed.

Feedback for the Azure Local Product Team

My organization recently updated our deployment workflows to align with the Microsoft change that moves the domain join operation into the Validation phase of the Azure Local deployment process. While we have adapted to this update, we would like to provide some important feedback regarding the documentation and communication surrounding this change.

Documentation Concerns

The current Microsoft Learn documentation does not clearly highlight that the domain join now occurs during the Validation phase. This phase executes configuration changes, yet the term “Validation” implies a non-destructive verification process rather than one that performs complex and difficult-to-reverse configuration changes. This discrepancy can cause confusion and create challenges during deployment for customers.

Recommendations

• Consider renaming the Validation phase to better reflect its role as a configuration step rather than just a verification step.
• At a minimum, include a clear warning in the official documentation stating that the Validation phase performs multiple irreversible configuration changes.

Communication on Breaking Changes

We also encourage the Azure Local team to improve advance communication regarding breaking changes in upcoming releases. Early, clear, and actionable notifications empower customers to prepare effectively, reduce support incidents, and avoid disruptions to critical projects.

To enhance communication, we suggest adopting the following best practices:

• Publish a detailed change log with explicit callouts for breaking changes at least one week before release.
• Provide clear guidance on necessary updates or adjustments customers must make in their environments and automation workflows before upgrading.
• Share this information proactively through official channels to reach all customers and deployment partners.
• Collaborate with partners to ensure effective dissemination of breaking change notifications.

We appreciate your consideration of this feedback.
Matt