Adding custom script extension when DSC extension already exists

Question

Hello,

I have a use case where I'd like to use a Custom Script extension on VMs that already have the DSC extension installed.

I've tested this, and found that the Custom script extension works as desired, but when I active the custom script extension via powershell, the DSC extension also goes to transitioning then successful. Is this expected behavior?
Are there any adverse effects from this?

I've run both DSC and custom script quite a bit, but not together so this is a bit foreign.

Thank you in advance!

Answer 1

Hi,
The two extensions are independent from each other. If you see that the DSC extension is changing states, I would suggest to check the activity log and see who has performed action on the extension of that time. May be there is some behavior in your script that is causing that or some coincidence that someone has executed the extension at the same time.

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.