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...
Use Copilot with Microsoft ToDo
It would be great if I could have Microsoft Copilot Pro talk to and be able to query these few responses. 1. What are my important task that I am missing? 2. What task do I need to focus on in the next few days? 3. Look at this project/doc/sharepoint file and add additional task to my ToDo that isn't currently on my list.
Copilot Agent with Salesforce
I am currently developing a custom agent in Microsoft Copilot Studio to streamline access to key information from our Salesforce sandbox, including Leads, Opportunities, I have successfully integrated Salesforce as a knowledge source using the Salesforce connector, authenticated via a service account with admin privileges in Salesforce. The integration is technically working as expected. However, I’ve encountered a security concern: At present, any user interacting with the Copilot agent can retrieve all data from Salesforce, regardless of their individual permissions in Salesforce. This appears to be due to the elevated privileges of the service account used for the connector. I would like assistance with configuring user-level access control within this integration. Specifically, I want to ensure that: Only authorized users can access specific Salesforce data through the Copilot agent. Users can only perform actions or retrieve records that their Salesforce permissions allow. Could you please guide me on how to properly implement permission scoping or data access control within Copilot Studio when using a high-privilege service account in the Salesforce connector?
I don't see conversation option in m365 chat
when i use this link https://m365.cloud.microsoft/chat?auth=2, which is m365 chat Vs Copilot.com. I do not see option for conversation where i can use mic to have a conversation with copilot. But when i use coiplot.com i see that option available. I tried to use copilot to figure it out but didn't get any answer which helped.
Copilot - Your education account is not yet supported
University sysadmin here. An increasing number of users with A5 licenses (Copilot Chat) are receiving the following error when trying to access https://copilot.microsoft.com/ "Continue as a guest or sign in with a personal account instead. Your education account <email address> is not yet supported." Is not impacting all users and seems to be transient. Cornell is also reporting the issue: https://itservicealerts.hosting.cornell.edu/view/7585 Workaround: User can sign in to Microsoft Teams and access the Copilot app without issue. -MattWhat the hack is a "Microsoft 365 Copilot Bizchat"?
I am taking a training course on learn.microsoft and this word "Microsoft 365 Copilot Bizchat" just came out of nowhere... I went few slides/pages of the training course and even googled it but there is no definition or clarification of it either sigh... What is that
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.
