Compare distinct AD and Azure tenant environments about aadconnectconfigdocumenter HOT 2 CLOSED

In my opinion, when comparing the different environments, only the changes to the sync rules are significant and anything else can be ignored. And that you can do just by updating just the connector name in one set of input config files as mentioned in the instructions on the homepage. However, if you are looking for something more to be treated as a match, I see that as an additional pre-processing activity. This could be done by writing a simple PowerShell script that does find and replace in all the config files as appropriate. So I'll close this issue now as I think an external pre-processing script is a better design for achieving your goals.

from aadconnectconfigdocumenter.

Modifying the output files does work but can be a mess keeping track of which edits were made to which set of files. I was thinking that adding a feature like this on the front end would be a cleaner solution.

from aadconnectconfigdocumenter.