This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 90%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPP%3C/text%3E%3C/svg%3E)
Hello,
We're developping a solution based over Azure Communication Service. It's been working for the past couple of month, but starting yesterday morning, the service stopped answering on token retrieval with a 401 error: Denied by the resource provider.
Nothing changed on admin panel, everything seems okay, but opening the endpoint ends on a page displaying
<h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0S3fKZAAAAAArwRMO++ChSZ9rDUv+/ZHrWVRPMjIxMDkwODE5MDQ1AEVkZ2U=
Nothing on azure fault page thought, and it's starting to be a bit long. Anybody encountered this issue ?
Hi @Pierre Pouzol , we are sorry to hear you're facing this issue. I also checked the Azure Status page and there are no active outages. Did you make any recent changes to your ACS?
Hi @Grmacjon-MSFT , not at all. Well I can't confirm that a 100% as it's something I worked on 3 months ago, but the person who got on that after me told me that nothing as been changed. Even stranger, I created a new ACS with the exact same configuration to test if it can be used as replacement, and yes, it works perfectly fine, while the old one is still unusable
Hi @Pierre Pouzol thanks for the update. can you please share the ACS configurations you used and the azure documentation you used so that we can try and repo this from our end?
-Grace
Hi @Grmacjon-MSFT not sure which configuration page you need. For the creation of the ACS itself, it really just was a "Next next ok" case, except for the region (US) and the subscription group we used, everything is default. For the documentation, we mostly based our work on this https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/chat/get-started?tabs=windows&pivots=programming-language-csharp.
Hi @Pierre Pouzol I wasn't able to reproduce this specific issue. This this issue will require deeper investigation offline. Could you please send us an email to AzCommunity[at]Microsoft[dot]com with the below details, so that we can enable a one-time-free support for you to work closely on this issue?
Email subject: <Attn - Grace >
Thread URL: <Microsoft Q&A Thread>
Subscription ID: <your Azure subscription id>
Please let me know here once the email is sent along with above requested details.
Thanks,
Grace
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(188.79999999999998, 16%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERV%3C/text%3E%3C/svg%3E)
Same problem.
Hi @Grmacjon-MSFT
I just sent the mail with the required informations.
thanks@Pierre Pouzol I responded to your email.
Hi Rafael Villa Verde , can you please give more details about your issue? is this a new or existing ACS resource? are you following this doc : https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/chat/get-started?tabs=windows&pivots=platform-azcli
As explained by Pierre in the first message, I also get a response code 401: Denied by resource provider. However, in my case, I use the email sending api (emails:send). I developed a php script that takes care of this and for a while it worked in some software I maintain. The source code for the hmac-sha256 subscription account can be found at https://github.com/hafael/azure-mailer-driver.
Likewise, following the authentication reference document found at https://learn.microsoft.com/en-us/azure/communication-services/tutorials/postman-tutorial, the same 401 result can be reproduced.
Hi Rafael Villa Verde thanks for your patience. when did you start facing this issue? Pierre's issue was resolved with no changes made from our end, so it is possible that the cause of his issue is the different from yours. Double check and make sure that your Communication Services token is valid and not expired.
Also, can you please post this issue as a new question so we can track this separately? feel free to tag me in the new question once it's created?
Hi @Grmacjon-MSFT ! My question was resolved. The 401 error occurred because I was sending the request body with a request body encoding failure on the client side. The issue was resolved by turning the body json/object/array into a string and including the Content-Type: application/json header in the request. A working version of the algorithm written in PHP can be found in the newly updated version of the library: https://github.com/hafael/azure-mailer-driver/blob/main/src/AzureMailerApiTransport.php#L300
Hi Rafael Villa Verde, thanks for the update and for sharing the solution that fixed your 401 error. I am sure others in the community will find it helpful.
Hi @Pierre Pouzol ,
As you shared offline, this issue was resolved, and all your ACS resources are now working.
-Grace