Import-CallQueue -> Error 401

[donky-bison]

Hi
I'm very excited about this app.
After deploying the app, I'm still facing problems using Import-CallQueue

• Using Power Automate I always get 401, even when authentication is set to "allow unauthenticatexd requests"
• Starting Import-callqueue direct in Azure Function works
• Can not use any other azure funtkion in Power Apps

Can you help me?

[JohanVeldhuis]

Hi @donky-bison,

It looks like that in that case the authentication piece might not be correctly configured. When you are running the workflow manually can you tell me which step exactly fails? What I suspect is that this might be an issue getting the secrets from the Azure Key vault however to confirm that I will need to understand which step exactly fails.

In the meantime you can validate the permissions on the Azure Keyvault by performing the following steps:

• go to the Azure portal
• search for the Key Vault used by the App
• select Access policies
• make sure the service account is listed
• validate the permissions assigned to the account are at least the get permissions

In addition to this validate the following secrets are listed on the Secrets section:

• TACO-appSecret
• Teams-service-account-name
• Teams-service-account-secret

Regards,
Johan

[donky-bison]

Hi Thank you for your help. The Access policies looks like that and "2 selected means" Get and List ***@***.*** Here are the defined secrets ***@***.*** Which steps failed running the workflow manually? ***@***.*** Best regards - Urs Egli Von: Johan Veldhuis ***@***.***> Gesendet: Freitag, 19. August 2022 16:38 An: OfficeDev/TACO ***@***.***> Cc: Egli Urs ***@***.***>; Mention ***@***.***> Betreff: Re: [OfficeDev/TACO] Imkport-CallQueue -> Error 401 (Discussion #19) Hi @donky-bison<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdonky-bison&data=05%7C01%7Curs.egli%40bithawk.ch%7Cb3ba7202d61d494c10f608da81f05fda%7Cb58f94a366ad4b34bd9e7d8af8addb7d%7C0%7C0%7C637965166652613980%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JiHk5wiHxVpJ4rxOZvypuNB0nCyb9V6cgStGghAPUZo%3D&reserved=0>, It looks like that in that case the authentication piece might not be correctly configured. When you are running the workflow manually can you tell me which step exactly fails? What I suspect is that this might be an issue getting the secrets from the Azure Key vault however to confirm that I will need to understand which step exactly fails. In the meantime you can validate the permissions on the Azure Keyvault by performing the following steps: * go to the Azure portal * search for the Key Vault used by the App * select Access policies * make sure the service account is listed * validate the permissions assigned to the account are at least the get permissions In addition to this validate the following secrets are listed on the Secrets section: * TACO-appSecret * Teams-service-account-name * Teams-service-account-secret * Regards, Johan - Reply to this email directly, view it on GitHub<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOfficeDev%2FTACO%2Fdiscussions%2F19%23discussioncomment-3432042&data=05%7C01%7Curs.egli%40bithawk.ch%7Cb3ba7202d61d494c10f608da81f05fda%7Cb58f94a366ad4b34bd9e7d8af8addb7d%7C0%7C0%7C637965166652613980%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ETwy0hvNbTnRByArAaOIK2%2FIfxDjto%2F8Tu%2FxTaVOS0g%3D&reserved=0>, or unsubscribe<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADRCHBYWH67W47EQBYVCM4LVZ6L3LANCNFSM57AC2OVA&data=05%7C01%7Curs.egli%40bithawk.ch%7Cb3ba7202d61d494c10f608da81f05fda%7Cb58f94a366ad4b34bd9e7d8af8addb7d%7C0%7C0%7C637965166652769691%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=WQJ6eMN%2BT6qQs6lwXYUuSxEghxGBKLmwA01Kk%2FVw5mg%3D&reserved=0>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[JohanVeldhuis]

Hi Urs,

Can you post a screenshot of the workflow failed so we can check which part failed?

Johan

[donky-bison]

Hi Johan Is this the screenshot you requested?? ***@***.*** Best regards - Urs Egli Von: Johan Veldhuis ***@***.***> Gesendet: Montag, 22. August 2022 08:58 An: OfficeDev/TACO ***@***.***> Cc: Egli Urs ***@***.***>; Mention ***@***.***> Betreff: Re: [OfficeDev/TACO] Imkport-CallQueue -> Error 401 (Discussion #19) Hi Urs, Can you post a screenshot of the workflow failed so we can check which part failed? Johan - Reply to this email directly, view it on GitHub<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOfficeDev%2FTACO%2Fdiscussions%2F19%23discussioncomment-3444391&data=05%7C01%7Curs.egli%40bithawk.ch%7Cfbcdf5cdf42f4916714d08da840bb2f7%7Cb58f94a366ad4b34bd9e7d8af8addb7d%7C0%7C0%7C637967483035035019%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=D4LcXV5NSVimoL1MzraV%2BOejSIxOVFq%2BD%2BsJdElX2AQ%3D&reserved=0>, or unsubscribe<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADRCHB6E2IIDVUS4UQCCOY3V2MQIXANCNFSM57AC2OVA&data=05%7C01%7Curs.egli%40bithawk.ch%7Cfbcdf5cdf42f4916714d08da840bb2f7%7Cb58f94a366ad4b34bd9e7d8af8addb7d%7C0%7C0%7C637967483035035019%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lloNtRimvJRTGVdcFeNFsTXKr8Z1Gl3l48%2Bv2GgMp9k%3D&reserved=0>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[JohanVeldhuis]

@donky-bison no but probably I should have been more clear. Please perform the steps below:

• go to make.powerapps.com
• in the left menu select flow
• search for the import all call queues workflow
• click on the 3 dots and select Run History
• find the latest run and click on the date/time to show the results
• find the object with the red cross
• expand the object completely and share the screenshot (WARNING: prior to sharing the screenshot make sure the value data is hidden by masking it)

Johan

[donky-bison]

Hi I hope this is ok ***@***.*** ***@***.*** Best regards - Urs Egli Von: Johan Veldhuis ***@***.***> Gesendet: Montag, 22. August 2022 15:08 An: OfficeDev/TACO ***@***.***> Cc: Egli Urs ***@***.***>; Mention ***@***.***> Betreff: Re: [OfficeDev/TACO] Imkport-CallQueue -> Error 401 (Discussion #19) @donky-bison<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdonky-bison&data=05%7C01%7Curs.egli%40bithawk.ch%7C598ad8642b6d4a08fb4c08da843f6700%7Cb58f94a366ad4b34bd9e7d8af8addb7d%7C0%7C0%7C637967705100595488%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=inv2KhIsqd4ypUdY3g3eQqugUHVby4DnqYEeOyGJtpQ%3D&reserved=0> no but probably I should have been more clear. Please perform the steps below: * go to make.powerapps.com * in the left menu select flow * search for the import all call queues workflow * click on the 3 dots and select Run History * find the latest run and click on the date/time to show the results * find the object with the red cross * expand the object completely and share the screenshot (WARNING: prior to sharing the screenshot make sure the value data is hidden by masking it) Johan - Reply to this email directly, view it on GitHub<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOfficeDev%2FTACO%2Fdiscussions%2F19%23discussioncomment-3447132&data=05%7C01%7Curs.egli%40bithawk.ch%7C598ad8642b6d4a08fb4c08da843f6700%7Cb58f94a366ad4b34bd9e7d8af8addb7d%7C0%7C0%7C637967705100595488%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qWuwiY1OP66KugXPSjNRhnCBb6Kma84Oq4FBSWt5J0M%3D&reserved=0>, or unsubscribe<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADRCHB465QP3L4IZ4KFSWA3V2N3UTANCNFSM57AC2OVA&data=05%7C01%7Curs.egli%40bithawk.ch%7C598ad8642b6d4a08fb4c08da843f6700%7Cb58f94a366ad4b34bd9e7d8af8addb7d%7C0%7C0%7C637967705100752046%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=z68f723QY43antPE8TbQ5lcdC%2FrVQp9SLKNiej1sZVA%3D&reserved=0>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[JohanVeldhuis]

@donky-bison it is probably me but I don't see a screenshot in this post

[donky-bison]

Hi

It should work know to see the screenshots

best regards

[JohanVeldhuis]

@donky-bison looks like the Azure Function url is not configured correctly. Please perform the following steps:

• go to make.powerapps.com
• select solutions from the left menu
• find the TACO app,select the 3 dots and select Edit
• in the list search for VAR - FunctionApp, select the 3 dots and select Edit
• validate the value specified in the Current Value field, for example if your Azure Function URL is https://azfunction.azurewebsites.net only use the host part, in this case azfunction
• after making the change click save
• run the import all call queues flow again

Johan

[donky-bison]

import all autoattendant
It seems to work now. I had to create a second AA otherwise I got an error in parsing Json - see grafic

import all call queues
error in parsing Json - see grafik 2 and 3

Many thanks for your help

[JohanVeldhuis]

@donky-bison good to hear it resolved your issue. We didn't thought about the scenario that there is only one AA or CQ so I will add that to our to do list to update the workflow to take this into account.

For the CQ issue please replace the JSON in the workflow with the one below:

{

"type": "array",

"items": {

    "type": "object",

    "properties": {

        "Name": {

            "type": "string"

        },

        "AgentAlertTime": {},

        "OverflowThreshold": {},

        "OverflowAction": {},

        "OverflowActionTarget": {},

        "OverflowSharedTextToSpeechPrompt": {},

        "OverflowSharedVoicemailAudioFilePromptFileName": {},

        "TimeoutThreshold": {},

        "TimeoutAction": { },

        "TimeoutActionTarget": {},

        "TimeoutSharedTextToSpeechPrompt": {},

        "TimeoutSharedVoicemailAudioFilePromptFileName": {},

        "UseDefaultWelcomeMusic": {},

        "WelcomeMusicFileName": {},

        "UseDefaultMusicOnHold": {},

        "MusicOnHoldFileName": {}

    },

    "required": [

        "Name"

    ]

}

}

Regards,
Johan

[donky-bison]

it works - thanks

[JohanVeldhuis]

@donky-bison good to hear it resolved the issue I have created an issue to make sure we fix this in the next version of the app.

[JohanVeldhuis]

Solution for this issue was:

• make sure the variable VAR - FunctionApp
• updated the JSON structure in the Import All Call Queues work flow --> bug is created