Bug: arm-cognitiveservices creates service endpoint using location instead of resource name about azure-sdk-for-js

[kazrael2119]

will check

[kazrael2119]

Hi @polinaouk ,
Here is the swagger example provided by the service team, we can see all the endpoints from response are created with location, I will try to test whether we can create the endpoint with service name

And you said "It works fine if I do it manually in azure portal." I don't know the steps to create any open ai resources as I have no permission to do that. You can give some screenshot of the endpoint creation in portal. I will ask @MaryGao whether we need add "Service Atthention" label to make service team aware this issue.

[polinaouk]

Hello @kazrael2119
Thank you for your response.
I see your point about the swagger. It is just quite unexpected behaviour as all other services in Azure which expose endpoints for example like App service, they create endpoints based on service name.

Additionally, why then is it different through Azure portal? Would really appreciate more clarity on this please.

Please find attached the prt screens below with portal experience:

[kazrael2119]

@polinaouk
In sdk code there's a optional parameter name customSubDomainName
So could you try to use the following code to create a account?

const account: Account = {
                kind:  "OpenAI",
                location: "swedencentral",
                sku: { name: "S0" },
                properties:{
                    customSubDomainName:""
                }
            };

            const openAiAccount = await cognitiveServicesManagementClient.accounts.beginCreateAndWait(
                "myFakeRGName",
                "testMondayoai",
                account,
            );

[polinaouk]

@kazrael2119 thank you so much for your help! it worked