Issues with creating resource accounts for AA and CQ

%3CLINGO-SUB%20id%3D%22lingo-sub-1041760%22%20slang%3D%22en-US%22%3EIssues%20with%20creating%20resource%20accounts%20for%20AA%20and%20CQ%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1041760%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20come%20across%20a%20curious%20issue%20that%20I%20don't%20seem%20to%20understand.%20When%20creating%20a%20resource%20account%20to%20be%20used%20for%20Auto%20Attendants%20or%20Call%20queues%20I%20get%20an%20error%20stating%20the%20account%20cannot%20be%20created.%26nbsp%3B%20This%20only%20happens%20if%20i%20use%20the%20tenants%20chosen%20domain%20for%20the%20username.%26nbsp%3B%20If%20i%20use%20the%20onmicrosoft%20domain%20it's%20fine.%26nbsp%3B%20This%20obviously%20isn't%20an%20issue%20as%20far%20as%20the%20functionality%20is%20concerned%20but%20i%20just%20don't%20get%20why.%26nbsp%3B%20Has%20anyone%20else%20experienced%20the%20same%20issue%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1041760%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESettings%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1041986%22%20slang%3D%22en-US%22%3ERe%3A%20Issues%20with%20creating%20resource%20accounts%20for%20AA%20and%20CQ%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1041986%22%20slang%3D%22en-US%22%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F455378%22%20target%3D%22_blank%22%3E%40BenRooke%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EDoes%20it%20throw%20an%20error%3F%20Have%20a%20screenshot%3F%3CBR%20%2F%3E%3CBR%20%2F%3EHow%20about%20if%20you%20create%20it%20on%20the%20onmicrosoft.com%20domain%2C%20add%20an%20alias%20of%20your%20custom%20domain%20and%20then%20flip%20the%20primary%20SMTP.%20Does%20it%20work%20then%3F%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1042173%22%20slang%3D%22en-US%22%3ERe%3A%20Issues%20with%20creating%20resource%20accounts%20for%20AA%20and%20CQ%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1042173%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F455378%22%20target%3D%22_blank%22%3E%40BenRooke%3C%2FA%3E%20-%20thanks%20for%20that.%20Could%20you%20%3CBR%20%2F%3E%3CBR%20%2F%3E1.)%20Retest%20that%20and%20see%20if%20it%20errors%20again%3CBR%20%2F%3E2.)%20Create%20a%20resource%20separately%20and%20link%20an%20AA%20to%20it%20to%20see%20if%20that%20works%3CBR%20%2F%3E%3CBR%20%2F%3ESounds%20like%20a%20bug.%20I%20just%20need%20a%20confirm%20before%20raising%20it.%20%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1042268%22%20slang%3D%22en-US%22%3ERe%3A%20Issues%20with%20creating%20resource%20accounts%20for%20AA%20and%20CQ%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1042268%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F455378%22%20target%3D%22_blank%22%3E%40BenRooke%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20ran%20into%20the%20same%20situation.%26nbsp%3B%20I%20think%20it's%20because%20there%20is%20no%20On-Prem%20Teams%20and%20it%20sounds%20like%20your%20domain%20is%20still%20on-prem.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3EI%20had%20to%20use%20the%20onmicrosoft.com%20as%20well.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20watch%20out%20using%20on-prem%20groups%20for%20Teams%20as%20those%20accounts%20will%20not%20be%20allowed%20to%20be%20added%20to%20on-prem%20sync%20groups.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1042028%22%20slang%3D%22en-US%22%3ERe%3A%20Issues%20with%20creating%20resource%20accounts%20for%20AA%20and%20CQ%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1042028%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F169605%22%20target%3D%22_blank%22%3E%40Christopher%20Hoard%3C%2FA%3E%26nbsp%3BNo%2C%20i%20didn't%20take%20a%20screen%20shot%20on%20the%20basis%20that%20it%20worked%20with%20the%20onmicrosoft%20details..%20The%20error%20produced%20simply%20stated%20that%20it%20was%20unable%20to%20create%20the%20account%20at%20that%20time..%20As%20a%20note%20this%20was%20while%20creating%20an%20AA%2C%20and%20creating%20the%20resource%20account%20from%20the%20setup%20rather%20than%20creating%20a%20resource%20account%20first%20and%20assigning%20it%20to%20the%20AA....%20if%20that%20makes%20sense....%26nbsp%3B%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20it%20did%20not%20interfere%20with%20the%20functionality%20of%20the%20AA%2FCQ%20I%20didn't%20give%20it%20a%20second%20thought.%20It's%20just%20a%20little%20confusing..%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

Hi All.

 

I have come across a curious issue that I don't seem to understand. When creating a resource account to be used for Auto Attendants or Call queues I get an error stating the account cannot be created.  This only happens if i use the tenants chosen domain for the username.  If i use the onmicrosoft domain it's fine.  This obviously isn't an issue as far as the functionality is concerned but i just don't get why.  Has anyone else experienced the same issue?

 

 

4 Replies
Hi @BenRooke

Does it throw an error? Have a screenshot?

How about if you create it on the onmicrosoft.com domain, add an alias of your custom domain and then flip the primary SMTP. Does it work then?

Best, Chris

@Christopher Hoard No, i didn't take a screen shot on the basis that it worked with the onmicrosoft details.. The error produced simply stated that it was unable to create the account at that time.. As a note this was while creating an AA, and creating the resource account from the setup rather than creating a resource account first and assigning it to the AA.... if that makes sense....   

 

As it did not interfere with the functionality of the AA/CQ I didn't give it a second thought. It's just a little confusing.. 

@BenRooke - thanks for that. Could you

1.) Retest that and see if it errors again
2.) Create a resource separately and link an AA to it to see if that works

Sounds like a bug. I just need a confirm before raising it.

Best, Chris

@BenRooke 

I ran into the same situation.  I think it's because there is no On-Prem Teams and it sounds like your domain is still on-prem.  

I had to use the onmicrosoft.com as well.  

Also watch out using on-prem groups for Teams as those accounts will not be allowed to be added to on-prem sync groups.

 

www.000webhost.com