Hey Rhys,
There are few things you can try.
- Check if you have the same issue with a confirmed Global Admin.
- Check your execution policy. You can use "Set-ExecutionPolicy Bypass -Scope Process" to temporarily bypass the policy within the scope of your current PowerShell session.
- Make sure you have all dependancy modules installed and imported.
- I'm not sure what parameter you are trying to set. But it could be a type mismatch in your command when setting the value for one of the attributes in the command.
If you can give us more insight in the attributes/parameters you try to run the command with, we could identify the issue more clearly.
Hope this helps you to resolve your issue.