Change to Microsoft Admin Center for Agents
Is anyone else who is managing agents within their company now seeing that you cannot see the publisher who created the agent on the main page? I also attempted to export a list and thought it would make it easy to get a full list of users who have created agents, but when exported the fields are completely different and there is no column for publisher. Earlier this week I manually took note of all publishers because that field was still showing on the "All Agents" page (which took many hours) but since Monday the UI has completely changed and more agents are showing now so I have to start over. We are trying to start our governance process for agents and a note was meant to go out to leadership of who on their team is creating agents but now I have to start from scratch with no visibility to who is making agents unless I click into each individual agent. Does anyone have a workaround as to how I can pull the list of publishers with their names? I don't understand why this field was taken out of the view because it gives to way to see who is creating agents across our large organization. Any help would be very appreciated.
From PC to Home Window: AI as Data Surgeon
Hello Copilot Community, I’d like to share a vision for the future of AI in Windows and beyond: evolving from a reactive assistant into a Data Surgeon — diagnosing, repairing, and reconstructing the lifeblood of modern life: data. 🩺 Diagnose Scan for corruption in files, registries, and hardware sectors Detect anomalies with machine learning and predict failures before they happen 🛠 Repair Auto-heal OS inconsistencies, registry errors, and driver mismatches Reconstruct corrupted files using backups, metadata, and contextual inference 🧬 Reconstruct Repopulate missing data from previous versions and cloud syncs Fill gaps in documents, databases, or media with AI-driven interpolation 🧑⚕️ Prescribe & Prevent Recommend preventive actions: backup schedules, hardware upgrades, cooling solutions Provide digital wellness reports — like a health checkup for your PC 🛤 Roadmap Toward the “Home Window” 2025–2027: AI-assisted diagnostics and repair tools 2027–2030: Household integration and predictive maintenance — the “Home Window Baby” stage 2030–2035: Cross-domain AI collaboration (social media, banking, utilities) 2035–2040: Fully fledged “Home Window” — essential for every modern home Discussion Prompt: How do you see Copilot evolving into this role? What technical milestones or safeguards would be essential? Could this align with Microsoft’s roadmap for Copilot in Windows and household AI?
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.
Amazing opportunity provided by MICROSOFT
Hi everyone recently I had found an amazing opportunity provided by Microsoft to the learn which most of us don't know please share this opportunity in your connection so that they also get benefited. https://learn.microsoft.com/en-us/training/browse/?resource_type=course&wt.mc_id=studentamb_478312 Thank youLimitation 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
