Jorge Olguin (super carnicerias hernandez sa de cv) asked a question.

Edited August 25, 2025 at 9:35 PM
MS Copilot IA, only two levels in rest calling.

Testing the waters for building agents that access our info, found that from copilot studio, there is a way to source a public knowledge origin. But when adding my own rest services, if rejects the three level deep path for our calling. xx.yy.zz.vv:4830/rest/<appname>/endpoint/...

Any idea?imagenAnd for extra problems, it states that info will go through Bing tech, so it will be available outside company.

 

What is everyone else doing about creating agents and uploading own info?

 

TIA

Jorge

  • 1 answer
  • 140 views
Roy Ellis, Stefan Drissen, and 2 others like this.

  • dina din (Customer)

    Hello,

     

    Copilot Studio restrictions – The Studio interface usually expects the endpoint to be either:

    A root-level resource (e.g., xx.yy.zz.vv:4830/rest)

    Or a single-level path after the base (e.g., xx.yy.zz.vv:4830/rest/<appname>)

    Deeply nested paths (/rest/<appname>/endpoint/...) sometimes get rejected because Studio is trying to parse the base URL and generate API documentation automatically. It may not follow paths beyond one or two segments.