NetworkError when deploying from Azure OpenAI Studio to Copilot Studio

Roy Remus Natavio 20 Reputation points
2024-09-10T03:48:33.0933333+00:00

I'm unable to deploy a chatbot from Azure OpenAI Studio to Copilot Studio due to NetworkError (see screenshot at the bottom).

Four days ago I have successfully deployed and published. I haven't tried deploying after that, until today. Even after several browser reloads, re-logins, and using incognito window, the same error persists.

Has anyone encountered the same and resolved it?

User's image

Azure OpenAI Service
Azure OpenAI Service
An Azure service that provides access to OpenAI’s GPT-3 models with enterprise capabilities.
3,042 questions
Microsoft Copilot
Microsoft Copilot
Microsoft terminology for a universal copilot interface.
282 questions
{count} votes

3 answers

Sort by: Most helpful
  1. Matthew Potocnik 0 Reputation points
    2024-09-17T13:27:24.85+00:00

    For me, after getting this error, I tested with an InPrivate window and it worked just fine.

    Logging out of all my MS accounts and closing/re-opening my browser (Edge) worked.

    It would seem being logged in to more than one MS account was the issue for me.


  2. Ioan Gageanu 0 Reputation points
    2024-09-24T13:12:20.4333333+00:00

    Using the new look Azure Open AI Studio portal, I have today the same problem in Australia East region. They clearly have some coding issues - check out the URL in the picture.

    Using the old look Azure Open AI Studio portal, I can deploy to Copilot Studio but I cannot make the Copilot work, it always responds that it cannot find the information in the supplied data - yet the original Azure Open AI Assistant does work ...

    error

    It seems to me that the problem is that the URL is incorrect and cannot be resolved by the DNS, hence the "network error".

    In fact, I believe that there is a typo in the code in the file main.30d08dd4.js at the line where a.a.arm is used

    typo

    when it should probably be g.a.arm like here

    g.a.arm

    Please investigate and fix. Also, probably testing procedures also need review. Thanks

    0 comments No comments

  3. Ioan Gageanu 0 Reputation points
    2024-09-24T14:49:33.6466667+00:00

    I suspect that the "network error" is indeed caused by the use of the incorrect URL which cannot be resolved by DNS - see pic in earlier post.

    It seems to me that the cause istypo

    a typo in the main.30d08dd4.js in the line where it uses a.a.arm

            baseQuery: Object(s.a)({
                baseUrl: "https://".concat(a.a.arm, "/")
            })
    

    when instead it should likely be using g.a.arm as used in

                Object(s.b)(g.a.arm, {
                    endpoint: {
                        tie: "management.azure.com",
                        test: "management.azure.com",
                        preprod: "management.azure.com",
                        preview: "management.azure.com",
                        prod: "management.azure.com",
                        gov: "management.azure.com",
                        high: "management.azure.com",
                        dod: "management.azure.com",
                        mooncake: "management.azure.com",
                        ex: "exreplacer",
                        rx: "rxreplacer"
                    },
                    authorizationEndpoint: {
                        tie: "https://management.azure.com/",
                        test: "https://management.azure.com/",
                        preprod: "https://management.azure.com/",
                        preview: "https://management.azure.com/",
                        prod: "https://management.azure.com/",
                        gov: "https://management.azure.com/",
                        high: "https://management.azure.com/",
                        dod: "https://management.azure.com/",
                        mooncake: "https://management.azure.com/",
                        ex: "exreplacer",
                        rx: "rxreplacer"
                    },
                    headers: {
                        "x-ms-client-session-id": Object(c.s)(),
                        "x-ms-client-request-id": l.a
                    },
                    authenticated: !0,
                    addAuthTokenToHeader: !0,
                    requestHandler: k,
                    responseHandler: P
                })
    

    g.a.arm

    Please investigate and fix and advise when done, thank you.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.