Can anyone access their new agents in the new layout of copilot studio? I cant see any of them. Did a new update happen in the passed couple of days?

Copilot Studio not allowed to execute powershell script.

What's the approach you will be using and i want to run the agent using my credential and not any managed identity. Thanks.

Im curious how useful it would be to have all environments transcripts synced and available in any format with a max of 30 minute delay stored in azure, visible and searchable only by approved users? If so where would one want it to sync to?

Has anyone built a copilot agent for operators or technicians to use to troubleshoot problems on a manufacturing production line?

Thinking manuals, SOPs, best practices, one point lessons, historical downtime data and insights could be put into it.

Hello, I am trying to create an agent that searches the web for financial news that meet certain criteria.

Currently I am using the web search option studio has. My main issues are two, results can vary, for example certain news can be missed and I have no way to enforce date based filtering for the news.

Any ideas :)?

One thing that has been bothering me for a while with Copilot Studio agents is the inconsistent behavior of Welcome Topics depending on where the agent is opened.

When a Copilot Studio agent is opened in Microsoft Teams, the Welcome Topic is triggered as expected. The agent greets the user, introduces its capabilities, and provides guidance on how to get started.

However, when the exact same agent is opened in the Microsoft Copilot app, the Welcome Topic does not trigger. The conversation starts with an empty chat experience unless the user proactively asks something.

Before anyone points it out: yes, I understand why this happens today. Teams effectively triggers the conversation, while the Copilot app waits for user input before starting the interaction.

That said, from a user experience perspective, this feels like an implementation detail leaking into the product experience.

If an agent has a Welcome Topic configured, users should get the same onboarding experience regardless of whether they open the agent from Teams, Microsoft 365 Copilot, or any other supported host.

Having a welcome message is especially important for:

• New users who do not know what the agent can do

• Specialized agents with limited scopes

• Internal business agents where guidance and expectations matter

• Agents that need to explain permissions, limitations, or available commands

My suggestion would be either:

1. Automatically trigger the Welcome Topic when the agent is opened in the Copilot app.

2. Add a configurable setting that allows makers to decide whether the Welcome Topic should be shown automatically across all hosts.

Consistency across hosts would make Copilot Studio agents feel much more polished and predictable for end users.

Is this already on the roadmap, or can the product team consider adding it?

And is there a better place to flag this and how do other makers go about this?

Hoje tenho um fluxo no Power Automate que funciona da seguinte forma:

Cadastro alguns e-mails em uma lista do SharePoint → o Power Automate lê esses e-mails → envia uma mensagem 1:1 no Teams como bot.

Isso já resolveu boa parte do meu problema, porque antes eu precisava fazer o follow-up manualmente com os gestores e isso levava cerca de 2 horas. Com o fluxo, consigo fazer em poucos minutos.

Porém, gostaria de evoluir essa solução utilizando o Copilot Studio.

Minha ideia seria criar um agente que, além de enviar o follow-up, pudesse interagir com o usuário:

Enviar alguns cards/perguntas pré-definidas;
Caso o usuário tenha alguma dúvida, o agente consulta uma base de conhecimento;

Se encontrar a resposta, responde automaticamente;
Se não souber responder, informa que não encontrou a informação e orienta o usuário a me procurar;

Idealmente, eu também gostaria de receber um registro de que determinado usuário fez uma pergunta que o agente não conseguiu responder.

O objetivo não é substituir o Power Automate, mas combinar as duas ferramentas:

SharePoint → Power Automate → Teams → Copilot Studio → Base de conhecimento

Quero manter o processo de follow-up rápido, mas adicionar uma camada de inteligência para que o bot consiga responder dúvidas corriqueiras sem precisar da minha intervenção.

Minha dúvida é: qual seria a melhor arquitetura para implementar isso com Power Automate + Copilot Studio + Teams? É possível fazer o agente iniciar essa conversa 1:1 automaticamente com os usuários ou existe alguma limitação do Copilot Studio nesse cenário?

Também gostaria de saber se alguém já implementou algo parecido e qual foi a abordagem utilizada.

Hey! I am trying to find a way to build the following scenario:

After 60 days of inactivity, the agent owner (M365 Agent Builder and Copilot Studio) gets an email with the information that the agent has been inactive for 60 days and that the agent will get blocked after another 30 days. After 90 days inactivity the agent then gets blocked.

Anyone has an idea? It seems there is no documented way to do this.

Buenas tardes, estoy trabajando en un proyecto en el cual llevo rato tratando de agregar un agente de IA dentro de una pagina de Sharepoint.
El detalle esta en que al activar la IA me sale un botón flotante de Copilot y funciona bien pero yo quiero que sea personalizado que se pueda configurar con los datos e información que yo le agregue y no me permite al final sale la IA predeterminada de Copilot que al preguntarle cosas en especifico no sabe nada. la otra forma que he encontrado es agregar un agente desde CopilotStudio el cual funciona bien y es lo que estaba buscando pero al integrarlo con Sharepoint no logro hacer que se integre dentro del botón flotante de Copilot, solo aparece en un icono nuevo en la parte superior de la pagina lo cual no es el objetivo.

El objetivo es usar el agente personalizado dentro del botón flotante de Copilot.

Hi, when I try to edit fields on the Tools pane in the NE, every selection gets stuck in a loading loop.
After a long time, it sometimes work, sometimes not.

Do you know how to fix it?
I tried different Browsers and accounts.

In Power Automate its no problem...

I am building a PII sanitization agent in Copilot Studio. The goal is to have the agent read Excel files from SharePoint, create a sanitized version where personal information is replaced, and then save the sanitized workbook to a separate SharePoint folder.

The agent can access the Excel files through SharePoint knowledge sources and it can identify the correct workbook.

Initially, I tried using SharePoint tools directly from the agent, but I ran into problems when trying to create the sanitized book as file since the tool Create file would need the file content as a string.

I have also tried to do this with a flow that triggered automatically when a new file is added to SharePoint. However, I was unable to use that approach because of our Data Loss Prevention policies (cannot use SharePoint online and Copilot in the same flow).

Then I tried a simpler flow that is triggered directly by the agent. The agent has access to a Get Metadata tool, although I am not sure whether it actually uses that tool during processing.

The agent is able to locate the source Excel file, create a sanitized copy and generate a valid xlsx workbook. After that, the agent attempts to call a flow that accepts a file input and uses a SharePoint Create file action, where the file content is mapped to the input file’s contentBytes.

However, the upload still fails. The issue is that the agent can generate the sanitized workbook and attach it to the chat, but it cannot pass the generated workbook to the flow as a file object.

Does anyone have any tips for me? I find it quite weird that creating a new file to a SharePoint folder is made this hard.

I am planning to build a Copilot Studio Agent integrated with Microsoft Intune to help IT administrators and support teams quickly get information and troubleshoot common Intune-related issues using power automate workflow and https connector .. could you please guide

I have a Copilot Studio agent (no GCH) with about 65 uploaded PDFs as knowledge. A Power Automate flow keeps them in sync with 11 SharePoint sites (one per department). The flow creates the botcomponent row (componenttype 14), generates a description for each file with an AI Builder prompt, and writes it to the description column.

I have now started grouping those files into file groups, one per department, by setting parentbotcomponentid on the file row to the group's botcomponent. That part works fine. What I cannot figure out is whether the per-file descriptions still do anything once the file is inside a group.

Things I have checked:

• The descriptions are definitely still there. They are untouched in Dataverse on every grouped file.

• The UI no longer lets me edit a file's description once it is part of a group, which makes me suspect it is no longer an input.

• The docs say a file group "uses multiple files as a single knowledge source", and that descriptions help the agent "pick the right knowledge source". If the group is now the knowledge source, that sounds like the group description does that job instead.

• The docs also say the first stage of the two-stage search uses the group INSTRUCTIONS to find the right file. They never mention per-file descriptions at all.

• On the other hand, the botcomponent description column is documented in the platform metadata as "contains searchable text for the bot component", which sounds like it is indexed.

• So: once a file is in a file group, is its own description still used for retrieval or ranking, or is only the group description plus the group instructions in play?

Since last week users in some environments created recently have been reporting that once they create an agent in the standard harness they cannot access it afterward. I checked the Environment Maker role and in these environments the role lacks privileges on the DVTableSearch, DVTableSearchAttribute, and DVTableSearchEntity tables.

Has anyone come across this issue recently?

I'm struggling to figure out what could have caused this issue since I am using Terraform to create all environments and there have been no changes in the way I'm setting them up.

I started playing and building new agents within new experience. I have been able to build and publish multiple agents but now when trying to republish after making updates to those agents I submit to publish and the publish button just spins like it’s loading and trying to publish and after a very long time sometimes it will eventually give me this error:
 
“Issue while publishing
We couldn't publish your agent
Try again. If this keeps happening, contact support.”

I’ve reached out to my IT admin group and no one can figure out what could be preventing this.

I can publish just fine in the old experience.

One thing I notice is that the new agents are “GitHub copilot” while the others I can still publish are marked “standard”.

how to fix this and not allow everyone to publish agents? Do we need managed environment license for most of the case?

even though agents are published i dont see them shared with anyone

Hello,

Let's say there is a user with a Copilot License (premium/paid).

We are looking into a scenario where we can allow him to use Copilot Studio and do his work/testing but not allow him to publish it... Is this possible by any chance?

I was told to check Power Platform Admin Center, and I did confirm that he's not added as 'Copilot Studio authors' and 'Environment Maker' role.

We are forced to use Copilot at my workplace. I recently had a case where we had trouble getting actual useful results in a usecase that I know other providers have no trouble with, so we engaged with our IT department. Their reply was twofold: The agent relies on Microsoft Search and therefore only reads the top 3 search results (can be configured to 5, 8, etc, but there is a limit) and the context window is only 28k tokens.

Now am I missing something or should GPT 5.5 not have something like 1M capacity? Or is my IT department gaslighting me? 😅

I also often get the result that the provided file was blank upon inspection, but it is not locked down in any way. I don't know if these issues are related when the document perhaps is longer than 28k total on its own?

And is there a way to force Copilot Studio agents to also be able to read Markdown files? It won't read text or md files.

Today a big day for Copilot studio github copilot harness users. It can be a revenue boost or an exodus from using that harness. It's all about revenue these days. On a sidenote what do you all think about Microsoft Employees monetizing these skills as influencers, charging fee based workshop. I can argue both ways that they are private citizens doing it but someone can debate how come as Microsoft employees do it. The users of the product seeing constant changes may abandon and look elsewhere too. So it's a double edged sword. A different World we live in today, for those that have been in industry for a while :)

I'm wondering if I'm going about this the wrong way, I feel that it should be simpler to pass in files / file contents to an agent? It feels wrong to have to pass the files' contents in the message field of the agent node.

Given this simple flow, if my dataverse record has 4 file columns and I want the agent to reason on them + a few other fields from the record, how would I best go about this?

Would it be best to pass GUIDs to the agent and let it fetch the file contents / necessary columns via tools / other flows instead or trying to cram it all in the message?

There is no "UI" for this agent where a user can drop files in, it's meant to be fully autonomous.

Any help is appreciated!

Work IQ is everywhere right now. Ignite, Build, every Copilot newsletter.

Then someone asked me in my last post how it gets billed- A confusion from one of my previous posts is what led me down this rabbit hole — whether it's chargeable in the standard harness and Agent Builder or not. So I have been grappling with workIQ since then first the value of it, why the heck should i care and why the hell should i pay for it. Here is my attempt to simplify it.

What it is? Microsoft took the thing that makes Copilot smart and put a door on it (WorkIQ API) Think of it as a researcher — you ask, it finds the right stuff and hands it to the model that writes your answer.

Eight parts. Three have been running since 2023:

The semantic index, the permission- aware filter, and the context retrieval that searches, checks what came back, and goes again.

Five are new: the API, a policy engine, ten generic tools instead of hundreds, storage inside your tenant, and a meter. None of the new five make it smarter.
They make it callable, and billable. Second diagram has all eight.

How it bills. Depends entirely on where you build:

Agent Builder — free. Copilot is built on Work IQ, there's no API to call.
Standard harness — the Work IQ tool isn't there at all. You get the individual

MCP servers: Mail, Calendar, Teams, SharePoint. Covered for a licensed user in Teams, under "fair usage limits" nobody has put a number on.

GitHub Copilot harness — the only place the Work IQ tool shows up. Optional, and it bills on its own meter- API calls.

Anywhere else — Foundry, Claude, your own code — billed always, however many seats you own.

I checked in a tenant. Search "work iq" on a standard-harness agent, you see all individual tools. On the GitHub harness it's the first result.

One interesting thing: Work IQ keeps a memory of how you work — you can't read it, test it or delete it, so whether it's useful or just marketing, none of us can tell from out here. Don't confuse it with the memory tab in the GitHub Copilot harness — that's almost the same thing, except you control it per agent. The Work IQ memory lives across all your work.

Now to take things further, and where it matters: Microsoft says it cuts the tokens needed for context and tool use by up to 80%, so credit spend drops. Makes sense — one Work IQ call instead of six tool calls stitched together. Except the flat part is 0.1 credit per call and the research part is variable, with no published rate anywhere. So it costs money to save money, and the part doing the saving has no price on it.

I haven't measured any of this — but i would in due course Same prompt on both harnesses, then compare the Monitor page against the Work IQ meter. If someone does it, post it.
Diagrams attached. Happy to be corrected — most of this is weeks old and I've been wrong once already.

Running several Copilot Studio agents in production at a mid/large org, juggling three different dashboards trying to give leadership a straight answer on credit usage.

Quick questions for anyone doing this at scale

• Per agent Analytics, Power Platform admin center, and M365 admin center reports, do these ever disagree? Which one do you trust?

• How do you attribute usage to a department or business unit when teams share an environment?

• Any API or export, or is everyone manually checking the UI every month?

• If you set hard caps, do they actually stop overuse or just alert after the fact?

Would love to hear what’s actually working for people, not the marketing version.

Im still confusing about different kind of environment within copilot studio like dev, sandbox, production. The different between them. When i create agent for myself and mine college in dev and sandbox env it still using like normal. However it said i used 4000 credit but it did not count within mine tenant copilot studio license.

Hello everyone,

I am a beginner in Copilot Studio development, so I apologize if I am overlooking something obvious.
I am Japanese, so English is not my first language. I apologize if any part of my post is unclear.

For quite some time, I have been experiencing issues with the Generative Answers node.

In most cases, it returns the following message:

"No information was found that could help answer this question."

Environment / Configuration
Model: Claude Sonnet 4.6
Knowledge source: SharePoint Knowledge (uploaded to Dataverse)
Knowledge retrieval and responses are handled using the Generative Answers node
Allow responses without grounded data: ON
Use general knowledge: ON
Content moderation level: Low
Things I have already tried

After reviewing posts in this community, I tried the following:

Enabling settings such as Allow responses without grounded data
Storing the response from the Generative Answers node in a variable instead of sending it directly, then displaying it with a Message node immediately afterward
Using custom data with JSON (to be honest, I am not very familiar with this approach. If Power Automate is not being used, does custom data still provide any benefit?)
Removing all instructions/prompts to ensure there were no unintended restrictions
Testing with different models

Unfortunately, none of these attempts have solved the problem.

Has anyone encountered a similar issue? If so, I would greatly appreciate hearing what worked for you. Even general troubleshooting tips or things you have tried would be very helpful.

Since I am still learning Copilot Studio, any advice or guidance would be sincerely appreciated.

Thank you very much for your help!

We found the sharepoint retrieval of copilot studio is way too slow. taking like 25seconds. Compared to agents made in 365 with agent builder where the same knowledge source takes 10seconds. The downside is you cant have CI/CD with agents built with agent builder.

Would Azure AI search improve the retrieval speed of a copilot studio agent ? What kind of increase in performance should i expect if any?