Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Enhancement Proposal for Configuration Comparison #4469

Open
jagatjb opened this issue Mar 20, 2024 · 0 comments
Open

New Enhancement Proposal for Configuration Comparison #4469

jagatjb opened this issue Mar 20, 2024 · 0 comments
Labels
Core Engine Enhancement New feature or request

Comments

@jagatjb
Copy link

jagatjb commented Mar 20, 2024

Description of the issue

When we do a configuration comparison, we get to know the changes based on the information in the individual parameters.

For example, EXOTransportRule, lets take a transport rule, and in the "From" parameter, lets say, one sender has been removed from among 50 senders and we do a configuration comparison report. In such case, the previous data and the current data is provided which is absolutely fine. But it gets difficult to read when there many senders in the "From" parameter in transport rules. So it possible to provide the details of only that specific sender being removed or added ?
This can be applicable for other parameters or multiple parameters with multiple values and most importantly, for multiple components and workloads.

Hope i was able to explain. Please let us know if this will be possible or not ?

Microsoft 365 DSC Version

1.24.313.1

Which workloads are affected

other

The DSC configuration

NA

Verbose logs showing the problem

NA

Environment Information + PowerShell Version

No response

@andikrueger andikrueger added Enhancement New feature or request Core Engine labels Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Core Engine Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants