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

Open
#124 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Domain
authentication, cli, release

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
PowerShell
Stars
1k
Forks
132
Avg merge
5d 19h
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/work-iq

All issues in microsoft/work-iq

Similar issues

More Security issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.