Workflows and App Builder Agents
Hey everyone, I have recently started using the Workflows and App Builder Agents, which are currently in preview through the Frontier programme and I would like to know your opinions on these tools as well. From my side, Workflows: didn't work once for me, most of the time, the flow is correctly generated, and connections are established but the flow fails to save. when it did save (that two times), it couldn't use the Outlook getEmails actions to pull information and errored out we don't have any DLP policies to block its use, so I don't understand why nothing is working here. last, it's no possible to edit the flow, which is not a great experience especially when trying to figure out what went wrong. App Builder: users need the permission to create a fresh sharepoint site for each app, this is a horrible experience for admin, as there could be hundreds new sites as users play around with the agent, why not allow users to pick an already established site, as all it does is create a list to store the information in? it's not possible to edit the app manually, so you're stuck talking to the agent for a long time to make changes that would take seconds in the PowerApps editor. when making changes through the editor, you can ask the agent to change a single thing in the app, then it 'kinda' understand and changes the entire thing either way, adding to the frustration. So all-in-all, both agents are a great concept, but they are still waaaay behind in what they promise.
Microsoft 365 Copilot licensing confusion
In the SharePoint Agent preview (ended in October 2025), Microsoft permitted unlicensed users to access SharePoint agents. I guess the reason for it was to enable organizations to evaluate agent functionality and provide feedback before licensing and billing requirements were applied (?). After the preview period concluded, it now seems that all users are required to have a Microsoft 365 Copilot Add-On license to interact with SharePoint agents. Users with, for example, a Microsoft 365 E3 license can only access the free version of Copilot (Copilot Chat), but do not have interaction privileges with SharePoint agents. A while ago, one of our CSP partners recommended us to buy a capacity pack and set up pay-as-you-go billing. In their opinion, this would replace the need for the Microsoft 365 Copilot Add-On license. However, we do not want to buy these expensive package unless we know for sure that this is the case. Can anyone answer the question: Does using a capacity pack and pay-as-you-go billing override user license requirements? Thank you ❤️Limitation of Copilot agent development in M365 developer tenants
I am using a M365 developer subscription and have hit a wall trying to develop a functioning Copilot agent. I was able to sign up for Copilot Studio trial license. This enables creation of M365 Copilot agent with knowledge held in SharePoint lists. However, not having 'Semantic Index' is a severe limitation that defeats the purpose of developer subscription. The agent being unable to use 'Enhance SharePoint Search' setting aka 'Semantic Index' aka vector embeddings means the agent is basically dumb and not an intelligent AI agent. After some research, I discovered the tenant needs at least one M365 Copilot license to enable 'semantic index'. To get my Copilot agent built, I decided to invest in this expensive license and then discovered a developer agent can neither have M365 Copilot or PAYG metered license. What this all means is that 'M365 developer subscription CANNOT be used to build a Copilot agent grounded in data in SharePoint'. You may be able to create a dumb agent with web search. A note that the agent I was building was not for a commercial customer. It was for my learning. By creating a proper agent, I will be able to showcase it in a YouTube video with the hope that some client somewhere may find it useful enough to pay for me as well as pay for Microsoft licensing, a win-win. I guess I will have to increase my investment fund, and sign-up for 'M365 Production Tenant + M365 Prod License Business or Enterprise + M365 Copilot + M365 Copilot Studio'. Seems like this type of development is a luxury only few could afford. Just thought to share as this may be useful for others trying to do the same.Copilot Connector for DevOps - Crawl Account = Search Admin?
Hi all, We’re about to set up Copilot Connectors for Azure DevOps (ADO) Wikis and Work Items across multiple organizations. During this process, we discovered that the account used to create the connector—requiring the Search Administrator role—is automatically designated as the crawl account. This crawl account must have read access across all projects within the ADO organization. Currently, we’re using our individual user accounts (with Search Administrator privileges) to create the connectors. However, we cannot use these accounts as crawl accounts due to access limitations. Ideally, the crawl account should be a service account with the necessary read permissions. The issue is that Microsoft’s configuration appears to require the same account to both create the connector and act as the crawl account. This would mean logging in with a service account that has Search Administrator rights, which is not a viable or secure option for us. Are we misunderstanding the setup? Is there a way to use our own accounts to create the connector and then specify a separate service account as the crawl account during configuration? We’re hoping someone can confirm that this separation is possible—and that we don’t need to grant Search Administrator privileges to a service account just to complete connector setup. Thanks - Grant.
usage price when adding Copilot chat-bot to our external web site
We have a public web site, where it contain some documentation in HTML pages and PDF files. now we want to develop a chat bot using copilot studio and embed this inside our public web site. but i have those questions:- Can external/anonymous users who visit our public web site, use the copilot chat-bot without having to login using Microsoft business account? 2. What about the usage price? how it will be calculated? Regards
What's difference creating Agent from Copilot page vs from Copilot Studio -> Copilot for M365?
Hello, I am learning about Copilot and was very confused by these two different ways to do it. My understanding is both are "Declarative Agents" which lets the Microsoft 365 Copilot do the most heavy lifting. Method 1. First way is to go to Copilot page and clicking 'Create an Agent' w3 Method 2: Going to Copilot Studio -> Agents -> Copilot for Microsoft 365 -> New Agent (Couldn't find a screenshot) Q1. Anyway, first, I created an Agent using the first Method 1 above, and now I see it on the Copilot page under 'Agents' section. However, when I go to Copilot Studio -> Agents -> Copilot for Microsoft 365, I don't see that Agent there. Is this normal and intended? Q2. Is an Agent created using the Method 1 only available to people who have Copilot license? (as long as they are shared; I see options are only me, anyone in the organization, and specific users in the organization) Q3. Could you please confirm agents created using either way above are both "Declarative Agents"? Sorry for the newbie questions in advance... I took the course MS-4010 and reviewed several posts but still confusing...SharePoint Knowledge Agent Vs Power automate AI builder
If we want to classify, summarize and extract key info from documents uploaded/edited inside a SharePoint document libraries. seems we can do this using AI builder inside power automate which get triggered when add/edit a document or using the Knowledge Agent, mainly the "Organize this library" option. can any one advice when you use each?Copilot Connector with Windows, Google Drive
Copilot in Windows now allow connections with Google Drive, Google Calendar and Google Contacts. It also allows connection with personal accounts of Outlook and OneDrive. You can now get insights and prompt Copilot based on these connections. You can test it out and give feedback to Microsoft to further improve Copilot's connection with third-party applications. You can learn more here - https://blogs.windows.com/windows-insider/2025/10/09/copilot-on-windows-connectors-and-document-creation/
