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 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/Microsoft 365 Copilot Usage Report API General Availability
The Copilot usage report Graph API is now generally available. Like the report APIs for the other workloads, the Copilot usage API helps to understand usage of some very expensive licenses. Even better, the usage data can be combined with data from other Microsoft 365 sources to produce interesting and valuable insights. All it takes is some PowerShell to knit everything together. https://office365itpros.com/2025/10/10/copilot-usage-report-api-ga/License Plans for Microsoft 365 Copilot
As Microsoft adds increasingly powerful AI capabilities, Copilot is becoming central to their strategy for powered productivity. But with power comes complexity: there are now several licensing plans depending on whether you’re an individual, a business, or an enterprise. Understanding what each plan offers — and which fits your needs — is key. https://dellenny.com/license-plans-for-microsoft-365-copilot/Introducing CoPilot Vision
CoPilot Vision has been introduced to view a page, and provide responses and information based on the content of the page You can read up on the article here - https://support.microsoft.com/en-au/topic/using-copilot-vision-with-microsoft-copilot-3c67686f-fa97-40f6-8a3e-0e45265d425f I did a test with different web pages and it gave an overview. There are also different kinds of voice settings. You can try this out, and I'd love to get your feedback on the use of CoPilot Vision.
We need help solving a critical integration gap between Microsoft 365 Copilot and Salesforce.
The challenge: We want Copilot to access Salesforce data (including custom objects) while honoring each user’s Salesforce permissions—profiles, field‑level security, and sharing rules. Current out‑of‑box connectors don’t support this. Using an all‑access integration account is a compliance risk. Why it matters: Copilot is only valuable if answers are both accurate and secure. If a user sees data in Copilot they shouldn’t in Salesforce, that’s a governance nightmare. What we’re looking for: ✅ Support for custom objects & fields ✅ Enforcement of Salesforce profiles, FLS, and sharing ✅ Delegated user authentication (Entra ID ↔ Salesforce) ✅ Works with Microsoft 365 Copilot grounding Questions: - Has anyone implemented this successfully? - Is there a Microsoft or Salesforce roadmap for delegated auth in Copilot connectors? - Do you know a partner or expert who can build this securely? Let’s make Copilot + Salesforce both powerful and compliant.Outlook Prioritize Inbox missing from client
Hey everyone, Just wanted to check for enterprise licensed users if you have access to the 'Prioritize Inbox' feature in Outlook. Unfortunately, it hasn't appeared in our client yet, also it's missing from the admin message center (used to be visible there). We have plenty of users who could take advantage of this feature and yet it is nowhere to be found. I have reached out to our Microsoft contact, who had it enabled, and stated that it's coming... coming when? All best, Kamil
Microsoft 365 Copilot Mic/Composer functionality for Android
Hi Everyone, We have been trialing Copilot, Claude, ChatGPT in our organization and finally decided to start buying some licenses for users, however we have noticed on android devices like samsung when you open Copilot and sign in it redirects you to the M365 Copilot app, after loading the app on our phones we notice you can no longer click the little mic icon and have conversations with Copilot, this is really frustrating and there seems to be zero information online about this, is this a lack of functionality or am I missing something in our tenant settings that would block the ability to use the mic function in the M365 Copilot app for Android? I can open the free version and have conversations with it but there is no history and its really annoying.
Part 00: Beyond Team Pride — Copilot Pages as the True Entry Point
In Part 0, I shared my personal motivation from an education experience. Building on that, here I want to highlight another reason — the fragmentation of Microsoft 365. The Problem The boundaries between apps are too strong, so to users they appear as completely separate worlds. The Challenge If this siloed culture continues, even new features will not solve the root issue — they will only add more complexity. My Proposal (Parts 1–3) That’s why I made my proposals in Part 1–3: Part 1: Simplify Copilot fragmentation Part 2: Vertical navigation to prevent getting lost Part 3: Dynamic sidebar for meetings Feasibility This is not an impossible idea. With Graph API and Fluent UI, plus existing side panels (e.g., Teams), unified lists, switching, and a meeting sidebar can all be implemented. It’s mainly integration and UX alignment, which makes it low-cost and high-impact. My Ask So please, prioritize user experience over team pride. If Copilot Pages becomes the true all-in-one entry point, Microsoft’s technology will shine even brighter — and users will finally say: “This is exactly what we’ve been waiting for.” 👉 Next: Part 4, “Thoughts Under a Cloudy Sky”, to explore the future vision. 00弾：メンツよりユーザー体験を ― Copilot Pagesを入口に 0弾では、自分の教育体験からの“きっかけ”を書きました。 その延長線上で、もう一つの理由――Microsoft 365の分断問題について整理します。 Microsoftの問題点 アプリごとの境界が強すぎて、ユーザーからは“別々の世界”に見えてしまう。 Microsoftの課題 この「縦割り文化」が続けば、新機能を出しても根本的な解決にはならず、かえって複雑さを増すだけです。 私の提案（第1〜3弾） だからこそ私は、第1弾〜第3弾の提案を出しました。 第1弾：Copilot乱立の整理 第2弾：縦スクロールUIで迷子防止 第3弾：会議UXの進化（動的サイドバー） 提案実現の可能性 これは実現不可能な話ではありません。 Graph API と Fluent UI、そして既存のサイドパネル（例：Teams）を組み合わせれば、統一リスト／切替や会議サイドバーは実装できます。 要は 統合とUX整理 であり、低コスト・高効果です。 最後にお願い どうか、メンツよりユーザー体験を最優先にしてください。 Copilot Pagesが本当のオールインワン入口になれば、Microsoftの技術はさらに輝き、ユーザーはこう言うでしょう。 「これこそ、私たちが求めていたものだ」と。 👉 次は第4弾、「曇り空に想うこと」 で、さらに未来像を描きます。
