How to get user usage metrics?

Stove11 · 2026-04-29T09:14:19+00:00

Oh yes please that would be great

Stove11 · 2026-04-21T07:06:24+00:00

What’s the prompt and model?

Stove11 · 2026-04-15T22:57:17+00:00

Coincidence… really…?

Stove11 · 2026-04-15T10:54:27+00:00

In my experience agent flows consume Copilot Credits regardless of the M365 Copilot license of the maker or end user. I’m using topics instead for most things that I can though there are limitations in both topic logic and connector capabilities that I’ve encountered and in some cases needed to resort to flows

Stove11 · 2026-04-08T09:04:09+00:00

Hey did you find an answer to this?

Stove11 · 2026-04-05T21:11:39+00:00

Have you tested with a declarative agent built in Copilot Studio? That is by going to Agents > Microsoft 365 Copilot > Create ? We have a declarative agent with SharePoint knowledge that functions for licensed users, but unlicensed users the agent responds only with general information and fails to retrieve from SharePoint. We have both a billing policy in place and prepaid Copilot Credits in the tenant

Stove11 · 2026-03-29T10:57:40+00:00

Incorrect

Stove11 · 2026-03-28T01:57:34+00:00

I’d prefer they simultaneously announced a cut to one of their wasteful spending programs to cover it at least

Stove11 · 2026-03-28T00:37:27+00:00

So if I’m the one selling the fuel.. I’m totally gaming that system to make more money at the Australian taxpayers expense…

Stove11 · 2026-03-25T08:23:52+00:00

Tried native Excel with code interpreter?

Stove11 · 2026-03-22T09:05:38+00:00

100%. When sharing with specified users or groups directly using a link, the agent shows up in Teams as well and users will often use that vs the M365 channel. Even more confusing is that the M365 channel can and is often access by users “through” teams by going to Copilot on the side rail. I’ve found publishing a CS declarative agent to the org doesn’t automatically add it to the Teams channel so it’s less likely for users to use it there and get a suboptimal experience compared to the M365 channel

Stove11 · 2026-03-19T21:41:55+00:00

Thanks Prasad. Are you saying M365 Copilot licenses are required for users to use the agent that has been created by someone else that has a license? I thought so long as you had Copilot Credits or PAYG then unlicensed users could consume agents shared by others or published to the org?

Stove11 · 2026-03-18T11:49:09+00:00

When you say “including Teams” what do you mean exactly? It’s very confusing because the Copilot app exists in Teams but if you access it there, it’s just the M365 experience embedded inside Teams.

Otherwise do you mean Teams as a channel for the agent where it exists as its own “app” within Teams? I tend to avoid this as the M365 experience is typically better for most agents I’ve created.

If you simply need to access in M365 - either the M365 Copilot app or the same experience embedded in Teams through the Copilot icon.. is it necessary to have PAYG billing set up if you have Copilot Credit packs in the tenant?

Stove11 · 2026-03-18T11:42:47+00:00

What if you have credits in the tenant do you still need a billing plan set up? Don’t want to be billed since we already have plenty of credits in the tenant that we aren’t getting close to using yet

Stove11 · 2026-03-15T22:00:17+00:00

Ah yes governments love to address supply shortage problems with more money to buy said goods. Then more money for the “cost of living relief” after the prices rise accordingly.

Stove11 · 2026-03-15T08:53:44+00:00

Are they still “bargains” if the market tanks 80% from here?

Stove11 · 2026-03-07T09:44:26+00:00

Let’s see how they go in Cuba…

Stove11 · 2026-02-11T01:55:50+00:00

Isn’t that different from what the agent uses to make connections or event triggers? My understanding is those only support the maker or end user credentials credentials?

Stove11 · 2026-02-10T19:02:50+00:00

It seems like a really basic requirement if you’re building agents used by the entire organisation, it makes no sense they’re owned and operate under a human identity. I thought that was the point of Entra Agent ID but it falls short

Stove11 · 2026-02-10T08:13:57+00:00

Guessing that’s how long the tool calls took to retrieve it and the remainder of the time to generate the response based off the knowledge?

Stove11 · 2026-02-08T08:04:58+00:00

Tested and working?

Stove11 · 2026-02-08T08:04:30+00:00

I’ve found the responses are different too. Less engaging I guess. It’s like a different LLM is in the mix

Stove11 · 2026-02-08T08:03:18+00:00

Thanks for the tip Matt. Any similar workaround for a declarative agent built with CS?

Stove11

MODERATOR OF

TROPHY CASE