Azure-docs: when create QnA Maker in Azure portal, returns "ServerFarmNotFound"

[xieofxie]

Screenshot as below

above error:

Thanks~

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 2431b5a7-e419-a331-b766-594294849502
• Version Independent ID: 92b9bdc0-348b-14c7-0f31-b5f06b252020
• Content: Set up a QnA Maker service - QnA Maker - Azure Cognitive Services
• Content Source: articles/cognitive-services/QnAMaker/How-To/set-up-qnamaker-service-azure.md
• Service: cognitive-services
• Sub-service: qna-maker
• GitHub Login: @diberry
• Microsoft Alias: diberry

[YutongTie-MSFT]

@xieofxie
Thanks for the feedback! We are currently investigating and will update you shortly.

[xieofxie]

Somehow it works for east us now and the problem may disappear magically later..

[YutongTie-MSFT]

@xieofxie Thanks for the confirmation. We will now proceed to close this thread. If there are further questions regarding this matter, please respond here and @YutongTie-MSFT and we will gladly continue the discussion.

[VladPapacostea-SM]

Hi guys. I am currently experiencing the same issue for the west europe region. Deploying from an ARM template. Same script works fine for east us.

[diberry]

@VladPScreenMedia Can you please open a feedback issue from the QnA Maker portal with this information?

@RohitMungi-MSFT FYI -

[VladPapacostea-SM]

Thanks @diberry
I have done that just now, with id: 119121324002573
@YutongTie-MSFT

[diberry]

@VladPScreenMedia Thank you - I'm going to close this now. #please-close

[kanika1894]

Hey,
Is the issue is not resolved yet?
Though it is working for EAST US but the validation is still failing for South Central US. Any plans to fix this? or we can assume that ServerFarms cannot be created anymore at South Central US via ARM Templates ?

[RohitMungi-MSFT]

@kanika1894 Could you try to use Subscription().SubscriptionIdinstead of subscription().id

              "serverFarmId": "[concat('/subscriptions/', subscription().id,'/resourcegroups/', resourceGroup().name, '/providers/Microsoft.Web/serverfarms/', variables('hostingPlanName'))]",
                "hostingEnvironment": ""
            },
            "tags": {
                "isqnamaker": "true",
                "[concat('hidden-related:', '/subscriptions/', subscription().id,'/resourcegroups/', resourceGroup().name, '/providers/Microsoft.Web/serverfarms/', variables('hostingPlanName'))]": "empty"
            },
            "dependsOn": [

To:

      },
                "name": "[variables('qnaMakerAppServiceName')]",
                "serverFarmId": "[concat('/subscriptions/', Subscription().SubscriptionId,'/resourcegroups/', resourceGroup().name, '/providers/Microsoft.Web/serverfarms/', variables('hostingPlanName'))]",
                "hostingEnvironment": ""
            },
            "tags": {
                "isqnamaker": "true",
                "[concat('hidden-related:', '/subscriptions/', Subscription().SubscriptionId,'/resourcegroups/', resourceGroup().name, '/providers/Microsoft.Web/serverfarms/', variables('hostingPlanName'))]": "empty"
            },
            "dependsOn": [

[VladPapacostea-SM]

Funnily enough, I am having this issue again today as well..

I am not being funny, but, it seems to be happening every friday ... and I am not a strong believer in coincidence. Maybe an underlying datetime issue ?

Another thing is, I've managed to find a region that worked on monday( went through about 6-7 regions), and finally deployed to UK South although I wanted it to be in West Europe.
So now I have a valid deployment in UK South, but for a laugh, I've tried to deploy another instance of my ARM template to UK South today ( different names and what not ), and failed miserably with the same issue mentioned above. Running it over the existing one, as an 'update' works perfectly fine though.