0.5.0-preview1 is not tagged as preview on npmjs.org and requires consenting to new permission

The new CLI version 0.5.0-preview1 now targets the new A2A API we released last week https://learn.microsoft.com/en-us/microsoft-365/copilot/extensibility/work-iq-api-overview
It was supposed to go out as a preview, but for reasons only I can be blamed for it wasn't tagged as a preview release and so those folks using an mcp config with npx that targets latest, they are going to get this new version automatically. Which is good because this release is full of goodness, but it also requires a new permission and a new Service Principal in the tenant.

I am working the team within Microsoft that manage NPM releases to remove the "latest" tag from this build, but if you have the version, you have two choices. Either target the 0.4.1 explicitly, or you can consent the new permissions in the tenant.

You can enable the new CLI in your tenant if you are an administrator by doing:

workiq auth consent WorkIQAgent.Ask

This will provision the service principal if necessary and then consent to this permission. Some customers have reported having some issues with the Windows Authentication Broker. If that is the case then you can disable the use of Windows Authentication Broker with the following command.

workiq config set disableBrokeredAuth=true

Apologies for the difficulties this may have caused.

No repository file or test is named; start by checking the npm release metadata for 0.5.0-preview1 and the CLI release process. Confirm whether the package still has the latest tag and whether the required permission and service-principal behavior are documented. Done means the preview is correctly tagged or the release impact is otherwise resolved.