Microsoft Copilot Studio Reviews

I use Microsoft Copilot Studio mainly for content creation and summarization for proposals I create. I also use it for workflows I have made for our organization and teams. There are agents built on Microsoft Copilot Studio which help in the Q&A part of bots. When asked a question, it gives a response based on the knowledge base it has.

The best feature about Microsoft Copilot Studio is the no-code aspect. It is easy to create your own agents and use cases. Even somebody who doesn't have prior knowledge of coding can easily and quickly create bots and deploy them in less than a few minutes. It comes with many security features that are taken care of by Microsoft. The summarization output and content are very useful and good.

Microsoft Copilot Studio helps individuals from a productivity gain perspective. There is a large part of assets usually available in the organization. All you need to do is look for the right search and content. Microsoft Copilot Studio helps with that very easily by fetching enterprise data and providing the right result. The text summarization feature allows you to condense lengthy documents into a few points or bullet points. When creating responses for presentations or customers in specific formats, Microsoft Copilot Studio helps create them with the right prompts.

We have achieved approximately 60 to 70% productivity gain using Microsoft Copilot Studio.

For analytics, I prefer using the Power BI platform instead of Microsoft Copilot Studio. When it comes to analytics, though it gives the right insight, the visuals are not of great quality, or sometimes they don't appear at all. For instance, when creating charts of sales on a quarter-on-quarter basis or month-on-month basis in a bar graph or pie chart, Microsoft Copilot Studio doesn't perform adequately. Anything requiring image creation or graphs and plots is not optimal.

The graphing features are missing in Microsoft Copilot Studio. Although image creation is available, it lags at times, similar to any other LLM module. When creating content based on graphs or CIO presentations, these features are not developed to a great extent.

I have been using Microsoft Copilot Studio for around two years.

Microsoft Copilot Studio is stable. In occasional instances, it hasn't provided the right response, rating between 7 to 8 on a scale of 10.

Microsoft Copilot Studio's scalability is excellent. When a large number of users access the same agents or bots simultaneously, the scalability is handled by Microsoft. We don't need to worry about the scalability aspect.

Customer service for Microsoft Copilot Studio rates nine out of 10, and technical support rates eight out of 10. Both services are good.

Positive

At an enterprise level, I did not use a different solution before Microsoft Copilot Studio. At a personal level, I use products such as Gemini, ChatGPT, and Perplexity very often.

My team and I use Microsoft Copilot Studio for productivity and repetitive tasks, which allows us to invest more time on things that matter to the customer rather than mundane, repetitive tasks. Low-level activities are handled by Microsoft Copilot Studio, allowing us to focus on tasks that require more brainpower. In terms of return on investment, we now focus more on things that matter to the customer.

There are several products equivalent to Microsoft Copilot Studio available in the market, such as Gemini, ChatGPT, and Perplexity. The advantage of Microsoft Copilot Studio is its integration with the Microsoft ecosystem. When documents are required from OneDrive or Word documents, the integration is handled on the back end by Microsoft, which provides an advantage.

The integration of Microsoft Copilot Studio with other current development environments rates four out of five. There are numerous charts we need to create, but the graphing features are missing. Though image creation is available, it lags at times, similar to other LLM modules. Creating content based on graphs or CIO presentations is not developed to a great extent. I rate Microsoft Copilot Studio an 8 out of 10.

I would describe a use case for Microsoft Copilot Studio as mainly developing AI agents.

The integration part in Microsoft Copilot Studio is something I really appreciate because it's very easy to integrate with anything, and the main reason we chose this Studio is its simplicity in developing and building workflows and interconnecting things, especially when it comes to public cloud; life is quite easy.

We are moving towards low-code, no-code, and my personal intention is that we should not waste much time in developing or scripting. Life should be quite easy so that our ideas can be put into reality instead of wasting time in testing, troubleshooting, and developing.

The main benefits Microsoft Copilot Studio provides for me are time-saving, and because of this time-saving, we need very little manpower.

The price for Microsoft Copilot Studio can definitely be improved, as small organizations find it very difficult to manage the subscription. For example, we are currently in a situation where we developed our AI agent, and everything is ready, but we wanted one feature, which is Excel export or Excel download generated by our AI agent, and we cannot do it because we need to purchase some extra subscription for that, and our organization is not willing to pay for it at the moment.

If we are purchasing some subscription, then at least most experimental or development level things should come as a package along with it, so we do not need to purchase anything extra.

Predictive analytic features in Microsoft Copilot Studio are still in the planning stage for us because we are not using them, but we want to use them.

I have been working with Microsoft Copilot Studio for approximately one year.

When rating stability from 1 to 10, I would rate it seven because we face some glitches, and when it comes to response, sometimes we experience delays.

When rating scalability from 1 to 10, it's quite flexible as we can easily move from the development environment to production. Development is very small and production is comparatively huge, but latency remains the only concern.

The initial setup for the product is very simple, as anyone can do it, and we need to invest only three to four hours, and then after that, we are on our own.

I am not currently using intelligent code assistance.

We are not that far with the data-driven insights from Microsoft Copilot Studio because we are in a very early stage, and AIOps is our main core area, so we use the Studio or any other products only on a need basis.

I can recommend the product, as they are improving significantly with more integrations.

At the moment, we are satisfied with Microsoft Copilot Studio because there is no competitor in the market.

I rate Microsoft Copilot Studio eight out of ten.

I am still at the early stage with Microsoft Copilot Studio, but I am fairly conversant in terms of the different tasks that I can create, and I am experimenting with almost all of the features of Studio and creating agentic AI agents, then integrating with Power Automate, as well as integrating with Instagram, Facebook, and other third-party applications. We are using Studio to act like our agent, capturing data, doing assessments, and reporting back all of the jobs given to the agent.

I am able to integrate Microsoft Copilot Studio with Power Automate, using Power Automate's connectors for integration. I am not exploring Microsoft Copilot Studio's default connectors, which are limited to what I am using it for, such as Teams, WhatsApp, emails, and Outlook. For third-party automation, I am using Power Automate. This is my choice, and I decided on this because I was more familiar with Power Automate, so I thought I would continue using it.

We are using the predictive analytics features of Microsoft Copilot Studio as part of our application use case. We fetch and collect the data, then perform a lot of predictive analysis and provide the report to the end customer.

I do not use an agent in Microsoft Copilot Studio as such, but I use AI a lot.

Microsoft Copilot Studio has helped enhance my development process quite a lot. My dependence on technical resources is getting lesser. There are a lot of things that we can actually ask our AI to verify, validate, or create code sometimes, or change everything, including documentation. I am not dependent on the team, especially for applications that are not very complex.

The user interface of Microsoft Copilot Studio has to be better—much better. I still need a front end on top of whatever I am creating, so I cannot say that it is a complete no-code or low-code development environment. The more we use it, the more we will get to know. Once it has gone into production, I will get to know more.

Pricing is another cumbersome thing because we do not want it to be very expensive. There are solutions that are open source and freely available, and people are using them. When we build with the hope that enterprises will like the enterprise-grade solution, they have to be ready to pay. The pricing should be friendly. Currently, I feel it is not all that friendly.

I feel that the pricing and licensing methods of Microsoft Copilot Studio are not very conducive. Enterprises who already have licenses may benefit from it, but new customers, SMB customers, and mid-market customers without licenses will find it difficult to absorb the cost because it becomes expensive based on usage. I do not have a solution to this, but I feel there is good scope where pricing can be better. The rationale behind my statement is that most Microsoft tools were primarily driven for enterprises, especially those that are not a must-have. Many applications, like Power Apps, were only used by enterprises or mid-sized companies. However, with AI coming in, everybody wants to use it, so there is a huge market available. If we do not price ourselves to that, we will miss the bus.

With Microsoft Copilot Studio, it has been about four months now.

This is my first attempt at using a solution for the same use cases.

So far with Microsoft Copilot Studio, everything is good. I do not have any complaints. It does sometimes get complex, but that is because of our learning; we are not one hundred percent knowing exactly how Copilot functions. We do a lot of trial and error, but while doing that, I have not faced any problems in terms of security, data loss, or unsaved data. There was just one time when the entire flow created was running and completely disappeared the next day morning, but I am not sure whether I should complain or if it was perhaps my error.

I am only hearing good things about the scalability of Microsoft Copilot Studio. I am using Microsoft Copilot Studio to do its own function, and I will be using it for scalability to ensure my application can take the load. It is not just the studio that is important, but Azure, its capacity, and memory will make it scale. Studio is only used to create all of this.

I have not taken any technical support from Microsoft for Microsoft Copilot Studio.

Neutral

This is my first attempt at using a solution for the same use cases.

I have not seen any return on investment with Microsoft Copilot Studio yet, as we are yet to launch it in the market. In another month, we will finish our testing and then launch it.

I am actually a Microsoft partner and work within the Microsoft ecosystem, so my first choice is Microsoft. I decided to choose Microsoft as my first bet because I can put it up on the marketplace and reach out to the Microsoft sales team for better sales support. Technology was not the differentiator; it was the trust in the Microsoft ecosystem that drove my decision.

I use OpenAI a lot, which makes me familiar with the OpenAI components, and I decided to go with Microsoft Copilot Studio. I did not use Copilot; I jumped straight into Microsoft Copilot Studio. We will also be deploying it on Azure and are using Dataverse, so all of the components are from Microsoft for the database.

I am not sure if I can pinpoint any one particular capability in Microsoft Copilot Studio as the most useful so far, since I have not compared it with anything else, making it difficult to say what is really good. I am just learning and using it, and it is straightforward and easy to use. There is a good amount of documentation, so I am happy with that.

Microsoft Copilot Studio has helped enhance my development process quite a lot. My dependence on technical resources is getting lesser.

The documentation is something I really like. The tutorials are good; we have gone through them. We have not done the certification yet because we wanted to get some hands-on experience first and then look for which certifications are important. For now, I think it is the foundation courses, tutorials, documentation, and of course, ChatGPT, which knows everything.

I would rate Microsoft Copilot Studio at an eight out of ten.

The use case involves intelligent code assistance, UI, UX, and integration parts.

The solution includes AI Search and AI Vision components. The user was asked about analytics features in Microsoft Copilot Studio and their helpfulness in the product.

The user was asked about satisfaction with functionality and potential suggestions for additional features.

The discussion involved various Azure products such as Azure File Storage, Object Storage, Azure Sphere, and Virtual Desktop.

The user was asked to rate the stability of Microsoft Copilot Studio on a scale from 1 to 10, with 10 being the best.

The user was asked about scalability aspects of the solution.

The user was asked to compare Microsoft Copilot Studio with competitors.

The deployment process was discussed and elaborated upon.

The discussion covered the purchase process and whether it was directly through Microsoft or through the AWS Marketplace.

The user was approached for a five-minute discussion about Microsoft Copilot Studio, noting time constraints due to a festival celebration in India.

The discussion focused on the main benefits that Microsoft Copilot Studio provides.

The review rating for this solution is 15.

Microsoft Copilot Studio is implemented for different scenarios, including straightforward and common scenarios. However, in cases where there is a need to work with RAG scenarios, high accuracy, and extensive documentation, more parameters for tuning and Azure integration are required.

Microsoft Copilot Studio's deep integration with Foundry allows building and deploying models seamlessly. Starting with Microsoft Copilot Studio for product projects, especially for POC and MVP, accelerates the creation and demonstration to clients, helping them interact with and understand the solution before discussing further improvements.

Microsoft Copilot Studio's integration with Foundry is a significant advantage. Building and deploying any model on Foundry and using it within Microsoft Copilot Studio without needing additional Azure-built components extends the capabilities of Microsoft Copilot Studio by leveraging the model catalog available in Azure.

The introduction of built-in connectors and native connectors has improved the predictive analytics features. Previously, using API connections was challenging, but the native connectors have enhanced the solution's functionality, making it a reliable product.

While Microsoft Copilot Studio can create documents and add information, it does not do so accurately, and this is an area that needs improvement.

The complexity of the licensing is another concern. Understanding how credits are spent based on different types of messages is unclear and complicated, particularly when explaining to non-technical customers unfamiliar with Copilot.

I am working as a Solutions Architect.

The predictive analytics features in Microsoft Copilot Studio are rated at the highest level because there is the ability to rely on its own functionality and many connectors. Before the introduction of these connectors, it was more difficult because using a lot of API connections was required, which is not ideal for solutions. With built-in connectors and native connectors now available, the experience has improved significantly. Overall, this is a good product. The review rating for this solution is 9.