Fix null string conversion in Export-M365DSCConfiguration for EXOMailboxAutoReplyConfiguration#5998 #6012
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.
…ation export
Pull Request (PR) description
This PR addresses an issue with the
Export-M365DSCConfiguration
cmdlet when exportingEXOMailboxAutoReplyConfiguration
. For some users, the export process was failing due to an invalid string conversion on one or more mailbox properties that can be$null
or not directly convertible to a string.The fix includes safely handling property values by explicitly casting them with null checks or string interpolation. This prevents runtime exceptions and ensures successful exports for all users.
This Pull Request (PR) fixes the following issues
Task list
Entry should say what was changed and how that affects users (if applicable), and reference the issue being resolved (if applicable).