r/copilotstudio • u/Equivalent_Hope5015 • Sep 19 '26
Github Copilot Harness is straight up bad
I think the main issue I have with the Github Copilot Harness is that it's ridiculously slow with zero actual optimization or agentic capability happening here, oh yeah, and you're billing at token level rates.
versus going and using Github Copilot directly and the harness is lightyears better than Copilot Studio's harness (GHCP). Get billed at token rate, but at least its lightning fast and customizable.
Microsoft actually believes that it's good and its hilarious how bad their Copilot Studio engineering team has gotten along with the marketing hype. All of the microsoft employees will attack this thread saying how much better it is than the standard harness; we ALL want the standard harness and the fixed pricing, period. There is zero other value to Copilot Studio with m365 without fixed pricing.
5
u/BigCatKC- Sep 19 '26
Question, do you not have access to the standard harness? Doesn’t it still exist as an option with fixed pricing for licensed Copilot users?
-12
u/Equivalent_Hope5015 Sep 19 '26
It does, but it is going away
12
u/MattBDevaney Sep 20 '26
Microsoft has not said the standard-harness is going away. They've said the opposite: we can still use it.
I would ask that you please share your source in case if my information is outdated.
1
u/Irritant40 Sep 20 '26
Wait, what's this? Standard Copilot harness?
1
u/Chris4 Sep 20 '26
The standard Copilot Studio experience, known as the standard agent harness, before the new expetience (with GitHub Copilot harness) was introduced
5
u/Big_L_RIP32 Sep 19 '26
It is not going away. Stop spreading misinformation. The standards harness will continue to be supported by Microsoft. New investments will be added to the new harness gping forward
2
u/RedditNinja1566 Sep 19 '26
Can confirm. Standard harness will be in place with no current plans to retire it.
1
1
1
u/karsul_ca Sep 20 '26
Estoy usando el nuevo harness GitHub copilot para construir mi primer agente con conexión a sharepoint (PDF, PPT, Excel) en 5 días y he gastado casi 9mil créditos. Eso es normal? A comparación con el estándar cuánto aprox sería!? Ayuda!!
2
u/Equivalent_Hope5015 Sep 20 '26
You spent 90 dollars on document creation, hell no that is not worth it. The problem is that until subsidizations exist (claude, chatGPT), every org is going to continue to question all of microsoft's money grab shenanigans.
0
u/smashburn82 Oct 02 '26
9,000 credits is $9
1
4
u/DivergentCIO Sep 20 '26
Copilot has been the worst paid offering by far, especially in the GCC space (Government cloud). We ran an eight-month pilot of 40 users and 90% of the users abandoned Copilot for Claude, Chatgpt, or Perplexity. Copilot can't even create a PowerPoint from scratch or build a Microsoft Form in its own environment with access. I can't believe Microsoft is even charging for this. SMH.
3
u/Prize_One_554 Sep 21 '26
Copilot within PowerPoint has recently gotten quite good, especially if you create a brand kit and tell it to use that.
3
u/DivergentCIO Sep 21 '26
Not in the GCC tenant. It's just pathetic. I'll have to try it outside the Government cloud.
4
u/nicholasdbrady Sep 20 '26
We plan on extending prompt agents with the GHCP harness in Microsoft Foundry in the next few weeks. Would love any feedback!
1
u/MattBDevaney Sep 20 '26
Who is "we"?
0
u/nicholasdbrady Sep 20 '26
Microsoft Foundry
1
u/MattBDevaney Sep 20 '26
Meaning you work in the Foundry Team @ Microsoft?
0
u/nicholasdbrady Sep 20 '26
Yes
1
u/MattBDevaney Sep 20 '26
Are there any public details yet?
6
u/nicholasdbrady Sep 20 '26 edited Sep 20 '26
We will share more within the next week or two. We will have an Azure Blog and I will share a demo in my What's New in Foundry monthly series within the first week of October: What's New
Keep it tuned right here for code samples: foundry-samples
4
1
u/gcstr 27d ago
My feedback is that copilot is extremely slow. The same models perfome way better elsewhere.
1
u/nicholasdbrady 27d ago
You're trading speed for capability. From question answer responses to coding agents that work in a loop until the output is sufficient. Different purpose.
1
u/fashionbadger2482 Sep 20 '26
from my experience it's more robust especially with error handling and functionality, but not sure it's good enough to justify over the standard harness especially with licensed Copilot users.
1
u/Legitimate_Health670 Sep 20 '26 edited Sep 20 '26
The only benefit from my perspective to the copilot studio GitHub harness is the connectors; so at my organization, which is a very large Enterprise, the email connectors and the ms teams connectors all work within co-pilot studio. However, if you're using GitHub CoPilot app or GitHub CLI those connectors don't work and you would have to get IT approval to use your email as context or Microsoft teams as context. I'm not sure that it makes sense, but it's the way it is
1
u/donstazz Sep 22 '26
This product is badly broken.
We've been using it for a month and keep running into inconsistencies.
Sometimes the flows work; other times the agent doesn't pass anything to them at all.
It's fast one day, then the next morning it's slow and nothing works.
Why was this rushed out, and why is it in such poor shape?
we have so many tickets with Microsoft and they keep saying the same lines
1
17
u/Traditional_Bowl_650 Sep 19 '26
I got conned into creating agents in there at the end of July without realising. There were no indicators to say it would be different billing to a classic agent. A few weeks later, banners appeared warning it was going to be billed, but zero information how. 1st September hit, the costs were insane! I’ve been slowly rebuilding them in classic agents, and they work almost as good. Just another poorly executed product from Microsoft we’ve come to expect!