It would be helpful to have the ability to filter out or identify already imported Intune policies when opening the import policy modal. Similar to how adding policies to a baseline excludes the policies already in the baseline. As we already have over 100 policies within our MSP tenant, it's challenging to see which ones we still need to import or missed importing.
Intune Policy Import Exclude Imported Policies
Excellent idea, Chris!
Are you thinking don't allow the import to complete? (i.e. You have selected policies that already exist in NMM. Please remove them before trying to import)
Or, make it more automatic and just exclude anything with a duplicate name and give a note after the import is finished that lists the policies that weren't imported? (i.e. The following policies were not imported because they have the same name as an existing policy: .... )
I wonder if there is a use case or if importing the same policy twice is possible. However, my issue was the inability to ensure I imported all the policies I created within the MSP tenant (that I wanted to import). Being able to filter out or essentially filter down to only those policies that have yet to be imported would be super helpful to ensure nothing is missed. Today, we test policies within our MSP tenant and then import and push them out to clients. This will be an ongoing challenge since the import modal does not denote and/or provide a way to filter out those that have already been imported.
Very good points.
Maybe having an option to compare what's in NMM vs your MSP Tenant (even if it's just a report?) would help?
Possibly add a prompt on import (i.e. These policies . . . already exist in NMM, do you want to import them again (Yes-Overwrite) (Yes-Rename) (No) (Cancel)) to handle duplicates?
There are definitely a lot of ways to handle this.
It'll be interesting to see if any of the other MSPs can provide their preference/use-cases.
Great idea. I'm not necessarily sure how that's done, but if you could just filter out ones where the name already exists, that would be a good start. Then you could turn that filter back off when you needed to re-import a new version of an existing policy.
Please sign in to leave a comment.
Comments (4 comments)