Home
%3CLINGO-SUB%20id%3D%22lingo-sub-566772%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-566772%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20does%20Microsoft%20plan%20to%20account%20the%20fact%20that%20some%20organizations%20will%20need%20to%20purchase%20or%20reserve%20additional%20E1%20and%20Phone%20system%20licenses%20to%20cover%20there%20resource%20accounts.%20Example%20to%20date%20we%20will%20need%20to%20order%20in%20123%20E1%20and%20Phone%20system%20licensees%20to%20migrate%20from%20SFB%20admin%20center.%26nbsp%3B%20And%20with%20and%20active%20rollout%20we%20have%20a%20need%20today%20for%20around%2010%20more%20with%20in%20the%20next%2030%20days.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-566812%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-566812%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F27883%22%20target%3D%22_blank%22%3E%40Wayne%20Stuebing%3C%2FA%3E%26nbsp%3Byour%20existing%20auto%20attendants%20and%20call%20queues%20do%20not%20need%20to%20be%20licensed%20before%20migration%2C%20they%20will%20continue%20to%20work%20as%20is%20when%20migrated.%20Newly%20created%20resource%20accounts%20only%20need%20to%20be%20licensed%20if%20they%20have%20a%20phone%20number%20associated%20with%20them.%20The%20cost-free%20application%20license%20model%20is%20work%20in%20progress%20and%20we're%20planning%20to%20release%20it%20soon.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-567878%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-567878%22%20slang%3D%22en-US%22%3E%3CP%3EHi.%3C%2FP%3E%3CP%3EWhat%20happens%20for%20companies%20that%20have%20%3CSTRONG%3EIVR%20in%20Exchange%202013%20OnPremise%20hybrid%3C%2FSTRONG%3E%20with%20S4B%20OnPremise%20hybrid%20with%20telephony%20and%20want%20to%20move%20to%20MS%20Team%3F.%20Is%20this%20type%20of%20scenario%20compatible%20with%20Microsoft%20Team%3F%3C%2FP%3E%3CP%3EFor%20example.%20Maintain%20IVR%20in%20Exchange%202013%20onpremise%20and%20migrate%20S4B%20to%20MS%20Team.%20Is%20it%20a%20compatible%20scenario%3F%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-569565%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-569565%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%26nbsp%3B%20Thanks%20for%20the%20reply%20but%20this%20is%20now%20causing%20us%20issues.%20I%20have%20a%20case%20open%20with%20Microsoft%20on%20it%20but%20we%20had%20ports%20to%20Microsoft%20in%20play%20and%20now%20as%20of%20this%20morning%20we%20have%20numbers%20out%20of%20service%20as%20we%20cannot%20assign%20the%20number%20to%20the%20account.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20tested%20with%20setting%20up%20accounts%20with%20E1%20%2B%20Phone%20System%20%2B%20Domestic%20calling%20plan%20and%20we%20still%20cannot%20assign%20a%20number%20to%20the%20account.%26nbsp%3B%20These%20are%20all%20Microsoft%20Service%20numbers%20I%20get%20that%20this%20change%20was%20needed%20to%20support%20things%20like%20PSTN%20dial%20out%20i%20assume%20but%20this%20was%20a%20very%20bad%20implementation%20again%20by%20Microsoft.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-569884%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-569884%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20auto%20attendant%20list%20in%20the%20new%20interface%20is%20in%20random%20order%2C%20with%20no%20way%20to%20sort%20or%20search.%26nbsp%3B%20%26nbsp%3B%20This%20simply%20won't%20work%20effectively.%26nbsp%3B%20(We%20had%2012%20pages%20of%20auto%20attendants%20in%20the%20old%20interface).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-570374%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-570374%22%20slang%3D%22en-US%22%3E%3CP%3EOn%20top%20of%20what%20Clinton%20just%20mentioned%2C%20there's%20also%20missing%20a%20phone%20number%20column%20and%20you%20now%20have%20to%20open%20each%20CQ%2FAA%20individually%2C%20to%20see%20the%20number%20that%20is%20assigned%20to%20it.%20Not%20very%20user%20friendly.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20if%20you%20are%20in%20the%20search%20text%20box%20you%20cannot%20use%20the%20HOME%20and%20END%20key%20on%20your%20keyboard%20because%20you%20lose%20focus%20of%20the%20text%20box.%20That%20is%20quite%20annoying.%20Please%20fix.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-570379%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-570379%22%20slang%3D%22en-US%22%3E%3CP%3EOur%20previously-working%20call%20queues%20aren't%20working.%3C%2FP%3E%3CP%3ENew%20call%20queues%20cannot%20be%20activated.%20Neither%20leaving%20unused%20licenses%2C%20nor%20explicitly%20assigning%20licenses%20allows%20selection%20of%20service%20numbers.%3C%2FP%3E%3CP%3ECome%20on%2C%20guys!%3C%2FP%3E%3CP%3EYou%20change%20how%20things%20work%2C%20release%20incomplete%20features%2C%20publish%20documentation%20that%20isn't%20valid.%20How%20are%20we%20supposed%20to%20pass%20this%20to%20our%20customers%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-570397%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-570397%22%20slang%3D%22en-US%22%3E%3CP%3EBojan%2C%20welcome%20to%20the%20club.%20Except%20that%20we%20are%20already%20the%20customer.%20And%20also%20the%20Q%26amp%3BA%2C%20apparently.%20Two%20things%20that%20usually%20don't%20mix%20well.%20We%20already%20opened%20a%20ticket%2C%20but%20it's%20been%20almost%20two%20weeks%20without%20real%20progression.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-570403%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-570403%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F27883%22%20target%3D%22_blank%22%3E%40Wayne%20Stuebing%3C%2FA%3E%26nbsp%3B%20operational%20auto%20attendant%20should%20continue%20working%20normally%20after%20migration%2C%20and%20creating%20a%20new%20resource%20accounts%20with%20a%20license%20and%20service%20number%20in%20the%20new%20environment%20based%20on%20the%20documentation%20should%20work%20as%20well%2C%20if%20either%20one%20of%20these%20scenarios%20is%20broken%20please%20open%20a%20ticket%20for%20tracking%20and%20support%20can%20help%20you%20with%20that.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20for%20the%20licensing%20requirement%2C%20this%20is%20not%20by%20any%20means%20a%20plan%20to%20monetize%20the%20applications%2C%20and%20we%20understand%20the%20inconvenience%20it%20introduced.%20However%2C%20due%20to%20the%20high%20demand%20for%20supporting%20hybrid%20numbers%2C%20multi-numbers%2C%20and%20all%20the%20benefits%20of%20the%20service%20upgrade%20we%20had%20to%20made%20the%20decision%20to%20not%20block%20these%20capabilities%20behind%20the%20app%20cost-free%20license%20model.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-570436%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-570436%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F65328%22%20target%3D%22_blank%22%3E%40Daniel%20Niccoli%3C%2FA%3E%26nbsp%3Bplease%20send%20me%20a%20private%20message%20with%20your%20ticket%20number%20and%20I%20will%20follow-up%20on%20it%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-570458%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-570458%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F65328%22%20target%3D%22_blank%22%3E%40Daniel%20Niccoli%3C%2FA%3E%26nbsp%3Bplease%20send%20me%20the%20ticket%20number%20in%20a%20private%20message%20and%20I%20will%20follow%20up%20on%20it%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-571053%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-571053%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F100655%22%20target%3D%22_blank%22%3E%40Clinton%20Woodward%3C%2FA%3E%20-%20totally%20agree.%26nbsp%3B%20We're%20working%20on%20the%20search%2C%20sort%20%26amp%3B%20filter%20capabilities%20on%20the%20interface%20we%20use%20from%20Teams%20admin%20center%20to%20enumerate%20the%20Auto%20attendant%20list.%26nbsp%3B%20Because%20we're%20moving%20to%20a%20%22lazy%20load%22%20model%20for%20that%20table%20(making%20page%20load%20times%20lower%20for%20tenants%20with%20lots%20of%20voice%20apps)%20sorting%20the%20list%20locally%20doesn't%20work.%26nbsp%3B%20Thanks%20for%20the%20feedback!!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-571088%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-571088%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F65328%22%20target%3D%22_blank%22%3E%40Daniel%20Niccoli%3C%2FA%3E%20-%20on%20showing%20the%20telephone%20numbers%20in%20the%20AA%2FCQ%20summary%20tables.%26nbsp%3B%20That%20one%20is%20frankly%20tough.%26nbsp%3B%20The%20service%20design%20is%20such%20that%20you%20can%20have%20a%20single%20app%20being%20serviced%20by%20multiple%20telephone%20numbers%20-%20those%20numbers%20are%20managed%20through%20%22Resource%20accounts%22%20-%20essentially%20non-user%20objects%20that%20allow%20all%20the%20call%20routing%20stuff%20to%20operate%20as%20expected.%26nbsp%3B%20So%20one%20could%20have%20a%20single%20app%20that's%20being%20serviced%20by%20a%20dozen%20or%20more%20numbers.%26nbsp%3B%20Dig%20the%20flexibility%20but%20enumerating%20this%20in%20the%20summary%20table%20is%20potentially%20super%20confusing%20and%20could%20adversely%20impact%20page%20loading%20times.%26nbsp%3B%20As%20such%20we%20made%20the%20call%20have%20them%20only%20in%20the%20detail%20view%20of%20the%20apps.%26nbsp%3B%20That%20being%20said%2C%20there%20are%20a%20few%20ways%20we%20could%20design%20this%20so%20the%20information%20is%20still%20available%20from%20the%20summary%20page%20but%20would%20still%20require%20a%20click%20to%20get%20to%20-%20thus%20avoiding%20the%20long%20load%20time.%26nbsp%3B%20Would%20that%20help%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOn%20the%20Home%2FEnd%20losing%20focus%20in%20the%20search%20box%20-%20I%20think%20you're%20right%2C%20as%20I've%20noticed%20some%20inconsistent%20behavior%20between%20objects%20across%20the%20site.%26nbsp%3B%20Which%20specific%20search%20box%20were%20you%20noticing%20the%20behavior%20being%20incorrect%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-571345%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-571345%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%26nbsp%3B%20I%20have%20a%20call%20open%20with%20support%20on%20this%20and%20there%20looks%20to%20be%20an%20issue.%20We%20still%20cannot%20complete%20the%20setup%20of%20new%20resource%20account%20as%20we%20are%20unable%20to%20assign%20numbers%20to%20these%20accounts%20even%20after%20using%20the%20guide%20on%20this%20page%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-US%2Fmicrosoftteams%2Fmanage-resource-accounts%3FWT.mc_id%3DTeamsAdminCenterCSH%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-US%2Fmicrosoftteams%2Fmanage-resource-accounts%3FWT.mc_id%3DTeamsAdminCenterCSH%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20the%20error%20that%20happens%20when%20you%20try%20and%20assign%20that%20number.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-left%22%20style%3D%22width%3A%20200px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F113568i20DD0810C60ECA9A%2Fimage-size%2Fsmall%3Fv%3D1.0%26amp%3Bpx%3D200%22%20alt%3D%222019-05-15%2015_11_46-Window.png%22%20title%3D%222019-05-15%2015_11_46-Window.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-572146%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-572146%22%20slang%3D%22en-US%22%3EWas%20there%20some%20kind%20of%20heads%20up%20that%20all%20this%20was%20happening%3F%20My%20staff%20was%20completely%20lost%20today%20with%20everything%20moved%20around%2C%20lots%20of%20functionality%20half-broken%2C%20and%20the%20inability%20to%20create%20AAs%20we'd%20been%20planning%20for%20with%20a%20whole%20new%20process%20and%20licensing%20requirements%20in%20place%20all%20of%20a%20sudden.%20What%20is%20the%20timeline%20for%20transferring%20out%20to%20pstn%20and%20for%20extension%20dialing%3F%20Will%20there%20be%20the%20ability%20to%20transfer%20from%20cloud%20AAs%20to%20sip%20addresses%20(onprem%20response%20groups)%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-572424%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-572424%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F27883%22%20target%3D%22_blank%22%3E%40Wayne%20Stuebing%3C%2FA%3E%26nbsp%3Bsend%20me%20the%20ticket%20number%20in%20a%20private%20message%20please%20and%20I%20will%20follow%20up%20on%20it.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-572452%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-572452%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F36671%22%20target%3D%22_blank%22%3E%40Wes%20Lazara%3C%2FA%3E%26nbsp%3Ba%20message%20was%20sent%20to%20all%20tenant%20admins%20in%20the%20Admin%20Message%20Center%20and%20the%20documentation%20was%20updated%20with%20the%20new%20experiences%202%20months%20ahead%20of%20the%20migration.%20all%20migrated%20applications%20should%20continue%20to%20work%20as%20is%2C%20if%20you%20have%20any%20of%20them%20broken%20please%20open%20a%20support%20ticket.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ETransfer%20to%20PSTN%3C%2FSTRONG%3E%20and%20extension%20dialing%20is%20work%20in%20progress%2C%20we%20expect%20to%20make%20them%20available%20by%20summer.%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EAA%20to%20RGS%20routing%20%3C%2FSTRONG%3Eis%26nbsp%3Ba%20bit%20tricky%20since%20RGS%20does%20not%20have%20a%20resource%20account%20(disabled%20user%20object)%20to%20route%20the%20call%20to.%20If%20the%20call%20is%20coming%20from%20hybrid%20or%20direct%20routing%20number%3B%20you%20should%20be%20able%20to%20assign%20a%20virtual%20number%20to%20RGS%20and%20route%20AA%20calls%20to%20it%20using%20DR%20or%20hybrid%20routing%2C%20this%20scenario%20is%20being%20tested%20and%20will%20update%20the%20documentation%20with%20the%20process%20soon.%26nbsp%3B%3CSPAN%20style%3D%22font-family%3A%20inherit%3B%22%3ECall%20coming%20to%20AA%20from%20a%20service%20number%20is%20not%20straightforward%20and%20need%20some%20code%20changes%20to%20support%20routing%20them%20to%20RGS.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-572476%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-572476%22%20slang%3D%22en-US%22%3EThanks%20Waseem%2C%20we%20will%20open%20a%20ticket.%20Would%20be%20great%20if%20the%20blog%20could%20post%20about%20the%20changes%20ahead%20(a%20follow%20up%20like%20this%20never%20hurts%20too)%20and%20the%20admin%20console%20itself%20maybe%20could%20broadcast%20them%20with%20some%20kind%20of%20banner...%20The%20tenant%20admin%20messages%20are%20nonstop%20-%20easy%20for%20stuff%20to%20slip%20through%20the%20cracks%20there.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-574829%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-574829%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20a%20ticket%20open%20but%20there%20appears%20to%20be%20an%20issue%20with%20Call%20Queues%20timing%20out.%26nbsp%3B%20For%20example%2C%20we%20have%20a%20call%20queue%20that%20should%20forward%20the%20call%20to%20another%20user%20if%20no%20one%20answers%20after%2015%20seconds.%26nbsp%3B%20It%20takes%20about%2090%20seconds%20before%20the%20call%20queue%20times%20out.%26nbsp%3B%20Interestingly%2C%20if%20we%20remove%20the%20call%20agents%20from%20the%20call%20queue%2C%20it%20times%20out%20at%20exactly%2015%20seconds.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20Tuesday%2C%20support%20told%20me%20they%20would%20provide%20a%20powershell%20script%20that%20would%20fix%20the%20issue%20later%20that%20day%20but%20am%20still%20waiting.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-574854%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-574854%22%20slang%3D%22en-US%22%3EWhat%20is%20the%20process%20of%20assigning%20a%20Direct%20Routing%20number%20to%20a%20Resource%20account%20for%20Auto%20Attendant%3F%20I%20tried%20Set-CsOnlineVoiceApplicationInstance%20cmdlet%20but%20no%20luck.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-575740%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-575740%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%26nbsp%3BCan%20you%20please%20share%20the%20Message%20ID%20of%20the%20message%20that%20was%20posted%20to%20the%20Admin%20Message%20Center%3F%20I%20watch%20it%20very%20closely%20and%20I%20don't%20recall%20seeing%20any%20advance%20notification%20about%20the%20change.%20Perhaps%20there's%20an%20issue%20with%20the%20Message%20Center%20in%20our%20tenant.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-576516%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-576516%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F159747%22%20target%3D%22_blank%22%3E%40Jeffrey%20Bladow%3C%2FA%3E%26nbsp%3Bthis%20is%20a%20know%20issue%20under%20investigation%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-576519%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-576519%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F30701%22%20target%3D%22_blank%22%3E%40Damian%20Kozlowski%3C%2FA%3E%26nbsp%3B%20you%20need%20to%20use%20S%3CSPAN%3Eet-CsOnlineApplicationInstance%3C%2FSPAN%3E%3CSPAN%3E%20-Identity%3C%2FSPAN%3E%3CSPAN%3E%20%3CU%3E%3CA%20tabindex%3D%22-1%22%20title%3D%22mailto%3Aappinstance01%40contoso.com%22%20href%3D%22mailto%3Aappinstance01%40contoso.com%22%20target%3D%22_blank%22%20rel%3D%22noreferrer%20noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eappinstance01%40contoso.com%3C%2FA%3E%3C%2FU%3E%3C%2FSPAN%3E%3CSPAN%3E%20-OnpremPhoneNumber%3C%2FSPAN%3E%3CSPAN%3E%20%3CU%3E%3CA%20tabindex%3D%22-1%22%20title%3D%22tel%3A%2B14250000000%22%20target%3D%22_blank%22%20rel%3D%22noreferrer%20noopener%22%3Etel%3A%2B14250000000%3C%2FA%3E%3C%2FU%3E%3C%2FSPAN%3E%2C%20we%20are%20updating%20the%20documentation%20to%20reflect%20the%20right%20Cmdlet.%26nbsp%3B%3C%2FP%3E%0A%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-576530%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-576530%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F80266%22%20target%3D%22_blank%22%3E%40Ryan%20Steele%3C%2FA%3E%26nbsp%3BThe%20message%20(MC172533)%20was%20sent%20to%20all%20customers%2C%20it%20expired%20on%204%2F30%20so%20it%20not%20in%20your%20admin%20center%20anymore.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-576556%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-576556%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%20Thanks%20that%20worked.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-576646%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-576646%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%26nbsp%3BThat%20Message%20Center%20notification%20was%20posted%20in%20January.%20In%20future%2C%20it%20would%20be%20helpful%20to%20have%20another%20notification%20closer%20to%20the%20actual%20migration%20date.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20should%20mention%20I%20am%20very%20grateful%20to%20have%20had%20the%20issue%20with%20answering%20Call%20Queue%20calls%20on%20a%203PIP%20phone%20solved%2C%20and%20we%20are%20very%20much%20looking%20forward%20to%20shared%20voicemail%20mailboxes%20and%20calling%20out%20to%20PSTN%20from%20an%20auto%20attendant!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-583110%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-583110%22%20slang%3D%22en-US%22%3E%2B1%20for%20alerts%20closer%20to%20rollout.%202%20months%20is%20an%20eternity%20given%20the%20pace%20at%20which%20you%20guys%20keep%20changing%20things.%20We%20have%20lots%20of%20broken%20functionality%20after%20this%20change%2C%20and%20support%20is%20telling%20us%20there%20were%20a%20number%20of%20provisioning%20mistakes%20made%20on%20the%20back%20end%20side%20-%20they%20are%20trying%20to%20sort%20it%20out%20now.%20Really%20hope%20this%20is%20not%20the%20new%20normal.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-584305%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-584305%22%20slang%3D%22en-US%22%3E%3CP%3EI%20hope%20this%20helps%20all%20of%20you%20guys.%26nbsp%3B%20I%20also%20had%20a%20bad%20migration%20weekend%20for%20AA's%20and%20CQ's%20and%20our%20teams%20admin%20portal%20still%20does%20not%20function%20correct%20but%20here%20is%20the%20fix%20for%20a%20lot%20of%20the%20pain.%26nbsp%3B%20While%20the%20teams%20admin%20portal%20documentation%20does%20not%20work%20properly%20the%20powershell%20does.%26nbsp%3B%20The%20big%20thing%20is%20it%20all%20has%20to%20be%20created%20via%20powershell%20including%20the%20creation%20of%20the%20resource%20account.%26nbsp%3B%20If%20you%20follow%20the%20documentation%20from%20start%20to%20finish%2C%20you%20can%20assign%20these%20numbers%20properly%20all%20through%20powershell.%26nbsp%3B%20I%20think%20it%20is%20an%20issue%20of%20the%20resource%20account%20not%20becoming%20a%20voiceapplicationinstance%20when%20created%20in%20the%20portal.%26nbsp%3B%20But%20when%20created%20in%20powershell%20you%20can%20use%20the%20voiceapplicationinstance%20correctly%20with%20no%20errors.%26nbsp%3B%20This%20has%20been%20painful%20for%20us%2C%20but%20have%20now%20got%20it%20all%20sorted%20by%20creating%20all%20new%20resource%20accounts.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FMicrosoftTeams%2Fmanage-resource-accounts%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FMicrosoftTeams%2Fmanage-resource-accounts%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-612733%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-612733%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20338px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F114265iA69D5EF564A45B9D%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22image.png%22%20title%3D%22image.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEither%20fix%20the%20GUI%2C%20put%20out%20a%20service%20advisory%2C%20or%20explain%20to%20your%20support%20team%20how%20to%20resolve%20the%20issue.%26nbsp%3B%20ticket%20%23%26nbsp%3B%3CSPAN%3E14398055%20if%20anyone%20is%20interested%20in%20details.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%22We%20can't%20load%20this%20resource%20account%22%20%22attempting%20to%20assign%20microsoft%20phone%20system%20service%20number%20to%20resouce%20account%22%20for%20the%20next%2010%20years%20of%20google%20search%20results.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-614616%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-614616%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%26nbsp%3BWe%20also%20run%20into%20various%20issues.%20A%20message%20center%20notification%20in%20January%20that%20expires%20end%20of%20April%20for%20a%20change%20that%20happens%20md%20May%20is%20not%20helpful.%20Further%20we%20had%20OrgAAs%20loosing%20DTMF%20configurations%20with%20the%20migration.%26nbsp%3BWe%20really%20would%20like%20to%20ask%20Microsoft%20to%20better%20plan%20and%20communicate%20such%20changes%20in%20the%20future.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-614671%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-614671%22%20slang%3D%22en-US%22%3E%22A%20message%20center%20notification%20in%20January%20that%20expires%20end%20of%20April%20for%20a%20change%20that%20happens%20md%20May%20is%20not%20helpful....We%20really%20would%20like%20to%20ask%20Microsoft%20to%20better%20plan%20and%20communicate%20such%20changes%20in%20the%20future.%22%20%2B1%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-615035%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-615035%22%20slang%3D%22en-US%22%3E%3CP%3EI%20can't%20seem%20to%20get%20direct%20routing%20to%20work%20with%20Calling%20queues%20or%20auto%20attendant.%20I've%20been%20able%20to%20assign%20numbers%20to%20the%20resource%20users%2C%20and%20the%20resource%20users%20assigned%20to%20application%20instances%2C%20but%20the%20application%20instances%20don't%20seem%20to%20come%20online.%20The%20sip%20logs%20in%20our%20SBCs%20tells%20us%20that%20the%20numbers%20for%20call%20queues%20in%20teams%20can't%20be%20found.%20And%20the%20sip%20users%20are%20not%20online%20when%20checking%20with%20teams%20and%20skype%20for%20business...%20what%20am%20I%20missing%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-615089%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-615089%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F344926%22%20target%3D%22_blank%22%3E%40randriksen%3C%2FA%3E%20in%20my%20case%20it%20took%2048h%20before%20I%20stopped%20getting%20404.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-615105%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-615105%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F30701%22%20target%3D%22_blank%22%3E%40Damian%20Kozlowski%3C%2FA%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22%22%3EIt's%20been%20about%2080%20hours%20since%20i%20set%20it%20up.%20still%20the%20same%20responses.%20I%20know%20the%20PSTN%20side%20all%20the%20way%20through%20the%20SBC's%20is%20correctly%20set%20up.%20I've%20got%20numbers%20assigned%20to%20normal%20users%20that%20work.%20the%20only%20thing%20that%20isn't%20working%20is%20calling%20queues%20and%20auto%20attendant.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22%22%3EI'm%20wondering%20if%20there's%20a%20step%20that%20i've%20missed%20or%20something%20since%20from%20what%20i%20can%20see%20it%20should%20be%20working.%20but%20it's%20just%20like%20the%20resource%20user%20isn't%20getting%20online%20or%20something.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-615464%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-615464%22%20slang%3D%22en-US%22%3EWhen%20I%20set%20this%20up%20I%20created%20a%20new%20Resource%20account%2C%20gave%20it%20E3%20%2B%20Phone%20System%20and%20run%20the%20below%20command%20and%20associated%20it%20with%20the%20Auto%20Attendant%20Set-CsOnlineApplicationInstance%20-Identity%20appinstance01%40contoso.com%20-OnpremPhoneNumber%20tel%3A%2B14250000000%20I%20was%20getting%20404%20for%20ages.%20From%20memory%2C%20I%20assigned%20the%20number%20on%20the%2016th%20and%20RNL%20kicked%20in%20on%20the%2019th.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-615466%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-615466%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F30701%22%20target%3D%22_blank%22%3E%40Damian%20Kozlowski%3C%2FA%3E%26nbsp%3Bso%20you're%20saying%20i%20should%20just%20wait%20and%20hope%20for%20the%20best%3F%20%3A-S%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-615474%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-615474%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F344926%22%20target%3D%22_blank%22%3E%40randriksen%3C%2FA%3E%20This%20was%20the%20case%20for%20me.%20As%20long%20as%20you%20have%20the%20correct%20licenses%20assigned%20to%20the%20resource%20account%20and%20you%20linked%20it%20to%20the%20AA%2C%20then%20it%20will%20most%20likely%20be%20replication%20issue.%20You%20can%20always%20open%20support%20case%20with%20MS.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-615894%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-615894%22%20slang%3D%22en-US%22%3E%3COL%3E%3CLI%3EYou%20can%20assign%20a%26nbsp%3B%3CSTRONG%3Ehybrid%20number%20%3C%2FSTRONG%3Eto%20AA%2FCQ%20(currently%20in%20preview)%3C%2FLI%3E%3C%2FOL%3E%3CP%3EAny%20idea%20when%20this%20feature%20will%20be%20rolled%20out%20-%20any%20way%20to%20get%20this%20for%20our%20tenant%20earlier%20than%20later%20as%20it's%20a%20feature%20we%20really%20want%20to%20take%20advantage%20of%20as%20we%20are%20just%20starting%20our%20on-premises%20to%20cloud%20migration%20but%20aren't%20quite%20ready%20to%20go%20to%20Teams%20yet%20(and%20will%20be%20using%20Direct%20Routing%20when%20we%20do).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-617892%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-617892%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%20I'm%20trying%20really%20hard%20to%20justify%20how%20Microsoft%20deemed%20this%20change%20acceptable.%20Why%20would%20you%20guys%20make%20such%20a%20sweeping%20change%20that%20breaks%20the%20basic%20functionality%20of%20the%20Cloud%20PBX%20service%20just%20to%20swtich%20us%20over%20to%20the%20undeveloped%20Microsoft%20Teams%20platform%20and%20then%20require%20us%20to%20license%20AA%20and%20CQ's%20while%20you%20figure%20it%20out%20how%20to%20make%20it%20free%3F!%3F%20HOW%20IS%20THIS%20AN%20ACCEPTABLE%20BUSINESS%20PRACTICE%20MICROSOFT%3F%20What%20the%20hell%20is%20going%20on%3F%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-618403%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-618403%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%26nbsp%3BIs%20there%20any%20idea%20when%20the%20queue%20wait%20will%20be%20fixed%3F%26nbsp%3B%20I%20get%20non%20stop%20complaints%20from%20customers%20that%20the%20time%20out%20is%20too%20long%20if%20someone%20isn't%20readily%20available%20to%20answer%20the%20phone.%26nbsp%3B%20Is%20there%20going%20to%20be%20any%20kind%20of%20announcement%20put%20out%3F%26nbsp%3B%20The%20tech%20support%20I%20am%20working%20seems%20to%20be%20unaware%20the%20lengthy%20timeout%20is%20a%20known%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-623011%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-623011%22%20slang%3D%22en-US%22%3E%3CP%3EHi!%20Very%20excited%20for%20this%20change%2C%20but%20I'm%20having%20issues.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20anyone%20having%20this%20issue%3A%20The%20command%20is%20run%20in%20Skype%20on-prem%20(for%20both%20Auto%20Attendant%20or%20Call%20Queue)%2C%20the%20AD%20object%20is%20created%20in%20Windows%20Server%20AD%20correctly%2C%20it%20syncs%20correctly%20and%20lands%20in%20AAD%2C%20but%20nothing%20has%20migrated%20over%3F%20I've%20ran%20the%20command%20on%20one%20Auto%20Attendant%20and%20one%20Call%20Queue%20and%20it%20still%20has%20the%20errors%3A%20%22WARNING%3A%20Active%20Directory%20object%20used%20for%20locating%20the%20organizational%20auto%20attendant%20(sip%3Aoaa_xx%40x.com)%20needs%20to%20be%20created.%20If%20you%20have%20not%20already%20done%20so%2C%20please%20execute%20the%20following%20cmdlet(s)%20on-premises%22.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt's%20been%20well%20over%2024%20hours.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-624011%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-624011%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F344926%22%20target%3D%22_blank%22%3E%40randriksen%3C%2FA%3E%2C%20did%20the%20404-error%20get%20resolve%20by%20replication%3F%20Having%20the%20same%20issue%20here.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-627868%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-627868%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F159747%22%20target%3D%22_blank%22%3E%40Jeffrey%20Bladow%3C%2FA%3E%26nbsp%3Bthe%20fix%20was%20completed%20and%20being%20rolled-out%2C%20expected%20to%20reach%20all%20tenants%20by%20Friday.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-627938%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-627938%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F343441%22%20target%3D%22_blank%22%3E%40jguel%3C%2FA%3E%26nbsp%3B%20you%20can%20start%20validating%20it%20now%2C%20its%20in%20public%20preview%20i.e.%20available%20to%20all%20customers%20but%20still%20under%20testing%20so%20we're%20not%20considering%20it%20%22General%20Availability%22%20yet.%20we%20expect%20to%20complete%20the%20validation%20and%20make%20it%20GA%20before%20the%20end%20of%20the%20month.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-631778%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-631778%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3ERegarding....%3CBR%20%2F%3E3.%20You%20can%20assign%20a%20%3CSTRONG%3Ehybrid%20number%3C%2FSTRONG%3E%20to%20AA%2FCQ%20(in%20public%20preview)%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20have%20a%20tenant%20that%20was%20cutover%20a%20week%20ago%20from%20legacy%20portal%20to%20the%20new%20V2%20portal.%20They%20have%20CCE%20deployed%20so%20we%20have%20assigned%20a%20HybridPSTN%20number%20to%20a%20Call%20Queue%20and%20sending%20PSTN%20calls%20via%20CCE%20to%20the%20Queue.%20PSTN%20-%26gt%3B%20SBC%20-%26gt%3B%20CCE%20-%26gt%3B%20CQ.%3CBR%20%2F%3EProblem%20is%20that%20media%20takes%2010%20seconds%20to%20establish%2C%20or%20usually%20longer%20which%20drops%20the%20call.%3C%2FP%3E%3CP%3EThey%20have%201000%20users%20on%20CCE%20and%20none%20have%20this%20delay%20so%20it's%20specific%20to%20the%20Call%20Queue.%3CBR%20%2F%3E%3CBR%20%2F%3EDo%20you%20think%20this%20is%20due%20to%20the%20%22public%20preview%22%20caveat%3F%3CBR%20%2F%3E%3CBR%20%2F%3EI've%20opened%20a%20support%20ticket%20with%20Microsoft%20via%20the%20O365%20portal%2C%20but%20I%20thought%20I'd%20mention%20it%20here.%3CBR%20%2F%3ECheers%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20505px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F115613i6170F3C3D4DC2F79%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22SKypePCClientLog_showingDelay.png%22%20title%3D%22SKypePCClientLog_showingDelay.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-631894%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-631894%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F138948%22%20target%3D%22_blank%22%3E%40Jason%20Jacobs%3C%2FA%3E%26nbsp%3Bsupport%20should%20be%20able%20to%20trace%20the%20issue%2C%20this%20is%20not%20an%20expected%20behavior.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-633144%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-633144%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F138948%22%20target%3D%22_blank%22%3E%40Jason%20Jacobs%3C%2FA%3E%20-%20if%20you%20don't%20mind%2C%20what%20Flow%20Chart%20call%20flow%20app%20is%20that%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-633188%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-633188%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3ETicket%20ID%2014232950%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Call%20queues%20and%20auto%20attendants%20seem%20to%20be%20working%20now.%3C%2FP%3E%3CP%3E-%20We%20still%20see%20the%20error%20'We%20can't%20load%20this%20resource%20account.'%20in%20the%20Teams%20admin%20portal.%3C%2FP%3E%3CP%3E-%20Calls%20are%20connected%20to%20the%20call%20queue%20(they%20hear%20the%20on-hold%20music)%20but%20it%20takes%205%20seconds%20for%20any%20call%20queue%20user's%20Skype%20to%20start%20ringing.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20we%20are%20not%20happy%20to%20having%20been%20migrated%20to%20Teams%2C%20when%20you%20cannot%20even%20provide%20license%20free%20number%20assignments.%20We%20were%20perfectly%20able%20to%20assign%20service%20numbers%20in%20the%20Skype%20portal%2C%20without%20being%20bothered%20to%20create%20and%20license%20user%20accounts.%20Not%20only%20did%20you%20remove%20a%20feature%20that%20we%20used%2C%20but%20you%20made%20it%20ten%20times%20more%20troublesome%20to%20create%20call%20queues%20and%20auto%20attendants.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-633335%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-633335%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%26nbsp%3Bit%20seems%20that%20agents%20can't%20opt%20in%20and%20out%20of%20queues%20after%20the%20move.%26nbsp%3B%20I%20will%20open%20a%20support%20ticket.%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fcqsettings%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fcqsettings%3C%2FA%3E%20shows%26nbsp%3B%3CSPAN%3EYou%20have%20not%20been%20added%20to%20any%20Call%20Queues.%20for%20all%20our%20agents.%26nbsp%3B%20Some%20of%20our%20agents%20were%20logged%20out%20last%20week%20when%20MS%20moved%20the%20AAs%20and%20Queues%20and%20now%20they%20can't%20login.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-633309%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-633309%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F85%22%20target%3D%22_blank%22%3E%40Jamie%20Stark%3C%2FA%3EI%20understand.%20Yes%2C%20maybe%20a%20button%20to%20click%20in%20the%20summary%2C%20that%20would%20show%20the%20numbers%20in%20an%20overlay%2C%20would%20be%20nice.%20Or%20something%20similar.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20search%20box%20I%20was%20talking%20about%20is%20the%20one%20on%20%3CSTRONG%3EUsers%3C%2FSTRONG%3E.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20there%20are%20more%20text%20boxes%20worse%20problems%2C%20that%20are%20really%20aggravating.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3COL%3E%3CLI%3EUnder%20%3CSTRONG%3EVoice%2FAuto%20attendats%2FBusiness%20hours%20call%20settings%3C%2FSTRONG%3E%2C%20when%20you%20want%20to%20redirect%20the%20call%2C%20you%20cannot%20use%20LEFTARROW%2C%20RIGHTARROW%2C%20SHIFT-LEFTARROW%2C%20SHIFT-RIGHTARROW%2C%20CTRL-SHIFT-LEFTARROW%20or%20CTRL-SHIFT-RIGHTARROW.%3C%2FLI%3E%3CLI%3EIf%20you%20select%20play%20menu%20options%2C%20you%20cannot%20use%20HOME%2FEND%20in%20the%20greeting%20message%20textarea.%3C%2FLI%3E%3C%2FOL%3E%3CP%3EI'm%20sure%20that%20I%20would%20find%20ten%20more%20if%20I%20had%20the%20time%20and%20will%20to%20look%20for%20them.%20It%20would%20be%20really%20helpful%20if%20you%20could%20%3CSTRONG%3Ereview%20the%20entire%20Teams%20admin%20portal%3C%2FSTRONG%3E.%20And%20don't%20forget%20the%20flyouts%20(Call%20queue%2FAdd%20resource%20account%2Fadd%20account%20flyout)%20Please%20don't%20mess%20with%20universally%20known%20keyboard%20shortcuts.%20This%20makes%20us%20nothing%20but%20miserable.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-633808%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-633808%22%20slang%3D%22en-US%22%3EI%20like%20where%20you%20are%20going%20with%20holidays%20but%20they%20are%20ABSOLUTELY%20WORTHLESS%20until%20you%20fix%20the%20available%20actions.%20I%20find%20it%20hard%20to%20believe%20that%20any%20companies%20really%20want%20the%20call%20to%20just%20disconnect%20during%20a%20holiday.%20Or%20transfer%20to%20a%20specific%20person%20in%20the%20organization%3F%20Who%20does%20that%3F%20I%20would%20think%20the%20first%20and%20default%20action%20would%20be%20that%20the%20attendant%20should%20just%20operate%20in%20%22After%20Hours%22%20mode.%20Why%20is%20that%20so%20hard%3F%20You%20need%20to%20stop%20letting%20developers%20decide%20what%20features%20are%20added%20and%20start%20listening%20to%20your%20users.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-633864%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-633864%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F77618%22%20target%3D%22_blank%22%3E%40Mark%20Linman%3C%2FA%3E%20there%20was%20an%20issue%20overnight%20that%20caused%20opt-in%2Fout%20problems%20for%20some%20tenants%2C%20it%20was%20resolved%20already%20and%20the%20fix%20rollout%20will%20be%20completed%20in%20couple%20of%20hours.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-637392%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-637392%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%20We%20are%20having%20issues%20with%20the%20amount%20of%20time%20a%20call%20is%20held%20in%20a%20Call%20Queue%20before%20being%20transferred.%20We%20have%20the%20maximum%20time%20set%20to%2015%20seconds%2C%20but%20the%20call%20is%20being%20held%20for%2070%20seconds.%20This%20is%20unacceptable.%20We%20have%20a%20ticket%20already%20opened%20for%20this%20issue%2C%20but%20it%20has%20not%20been%20taken%20care%20of.%20Ticket%20%23%26nbsp%3B13441387.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-637889%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-637889%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20482px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F115816i410DEC8D75F26184%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Holiday%20AA%20issues.jpg%22%20title%3D%22Holiday%20AA%20issues.jpg%22%20%2F%3E%3C%2FSPAN%3E%3CBR%20%2F%3EWe%20can%20not%20change%20the%20time%20of%20the%20day%20the%20announcement%20will%20start.%20We%20want%20to%20start%20at%203%3A00%20PM%20EST%20tomorrow.%20How%20to%20change%20it%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-637907%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-637907%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%26nbsp%3BI'm%20still%20waiting%20on%20a%20response%20from%20you.%20I'd%20like%20to%20know%20what%20product%20development%20team%20approved%20this%20botched%2Fforced%20chnage%3F%20Whatever%20happened%20to%20beta%20testing%20and%20ensuring%20QC%20before%20releasing%20out%20to%20production%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-638147%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-638147%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%20I%20know%20the%20assigning%20of%20a%20hybrid%20number%20is%20still%20%22public%20preview%22%20so%20maybe%20that%20is%20still%20the%20issue%20but%20I%20still%20can't%20get%20this%20to%20work%20at%20all.%20Seems%20like%20some%20people%20have%20gotten%20it%20to%20work%20somewhat%20but%20for%20me%20nothing%20about%20it%20works.%20I%20did%20have%20a%20ticket%20in%20but%20at%20that%20time%20I%20believe%20it%20was%20still%20just%20preview%20and%20they%20said%20to%20wait.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-638238%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-638238%22%20slang%3D%22en-US%22%3E%40Toyuwa_Harris%20It%20looks%20like%20you%20have%20to%20use%20the%20%22Holidays%22%20table%20located%20under%20the%20%22Org-wide%20settings%22%20menu%20option%20to%20set%20the%20date%2Ftime.%20Can%20I%20ask%20you%20which%20action%20you%20plan%20on%20using%20in%20your%20holiday%20setup%3F%20Disconnect%20or%20redirect%3F%20I%20have%20been%20arguing%20since%20day%20one%20of%20the%20new%20auto%20attendant%20(almost%201%20year%20ago)%20that%20the%20holiday%20feature%20is%20worthless%20because%20the%20actions%20are%20too%20limited.%20Hang%20up%20on%20the%20caller%3F%20Redirect%20to%20a%20specific%20user%3F%20I%20have%20yet%20to%20receive%20any%20reply%20from%20Microsoft%20on%20any%20of%20my%20posts.%20Crickets...%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-638992%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-638992%22%20slang%3D%22en-US%22%3E%3CP%3EOur%20call%20queues%20now%20timeout%20right%20at%2060%20seconds%20which%20is%20an%20improvement%20from%20the%2090-120%20seconds%20from%20before%2C%20but%20I%20really%20hope%20that's%20not%20the%20%22fix%22%26nbsp%3B%20The%20call%20queue%20is%20set%20to%20Timeout%20at%2015%20seconds.%26nbsp%3B%20If%20you%20remove%20the%20call%20agents%2C%20it%20times%20out%20right%20at%2015%20seconds.%26nbsp%3B%20If%20I%20change%20the%20timeout%20to%2090%20seconds%2C%20it%20takes%20almost%202%20minutes%20to%20timeout.%26nbsp%3B%20There%20are%20some%20upcoming%20features%20I'm%20excited%20about%2C%20but%20it's%20getting%20tough%20explaining%20to%20management%20these%20recurring%20hiccups.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-639039%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-639039%22%20slang%3D%22en-US%22%3EIs%20anyone%20having%20an%20issue%20where%20it%20doesn't%20timeout%20to%20voicemail%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-639179%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-639179%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F159747%22%20target%3D%22_blank%22%3E%40Jeffrey%20Bladow%3C%2FA%3E%26nbsp%3Bwe%20have%20been%20dealing%20with%20the%20same%20issue%20before%20the%20move%20to%20Teams.%20It%20is%20very%20frustrating%20that%20Microsoft%20seems%20not%20to%20care.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-639666%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-639666%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F159747%22%20target%3D%22_blank%22%3E%40Jeffrey%20Bladow%3C%2FA%3E%20-%20you%20guys%20seem%20to%20have%20timeout%20issues%2C%20but%20does%20it%20actually%20time%20out%20to%20a%20person%20in%20your%20organization%20%2F%20voicemail%3F%20With%20the%20CQ%20that%20migrated%20over%20to%20Teams%20we%20can't%20get%20the%20timeout%20to%20actually%20hand%20off%20to%20the%20voicemail%20we%20need.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-642447%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-642447%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F159747%22%20target%3D%22_blank%22%3E%40Jeffrey%20Bladow%3C%2FA%3E%26nbsp%3B%20I%20mentioned%20you%20in%20a%20comment%20on%20Tuesday%20regarding%20the%20timeout%20issue%2C%20the%20bug%20was%20fixed%20and%20rolling%20out%20started%202%20days%20ago%2C%20and%20expected%20to%20cover%20all%20customers%20by%20tomorrow.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-642451%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-642451%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F92230%22%20target%3D%22_blank%22%3E%40Mike%20Dominik%3C%2FA%3E%20we%20are%20rolling%20out%20new%20features%20that%20can%20be%20used%20for%20holiday%20treatment%2C%20they%20are%20listed%20above%20in%20this%20blog%20(Transfer%20to%20PSTN%2C%20Voicemail).%20Would%20appreciate%20your%20feedback%20on%20what%20else%20would%20you%20expect%20to%20have%20as%20a%20holiday%20treatment%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-642453%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-642453%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F343441%22%20target%3D%22_blank%22%3E%40jguel%3C%2FA%3E%26nbsp%3B%20if%20you%20post%20the%20process%20you%20followed%20or%20the%20error%20you're%20getting%20perhaps%20someone%20in%20the%20community%20can%20help%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-642465%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-642465%22%20slang%3D%22en-US%22%3E%3CDIV%20class%3D%22lia-message-author-avatar%20lia-component-author-avatar%20lia-component-message-view-widget-author-avatar%20UserAvatarWrapper%22%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20display%3A%20inline-block%3B%20float%3A%20left%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2014px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20padding-right%3A%2010px%3B%20position%3A%20relative%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F93194%22%20target%3D%22_blank%22%3E%40Edmundo%20Pena%3C%2FA%3E%20the%20changes%20were%20tested%20and%20validated%20with%20customers%20through%20the%20validation%20program%20for%203%20months%2C%20and%20rollout%20was%20controlled%20by%20quality%2C%20which%20is%20why%20it%20took%201.5%20months%20to%20complete%20the%20rollout.%20Unfortunately%20some%20of%20the%20bugs%20were%20not%20discovered%20until%20after%20the%20service%20was%20made%20generally%20available.%20To%20your%20question%20on%20the%20team%2C%20I'm%20the%20product%20owner%20for%20these%20services%2C%20and%20I%20do%20apologies%20on%20behalf%20of%20the%20team%20for%20the%20inconveniences%20that%20impacted%20your%20business.%20If%20you%20have%20an%20outstanding%20issue%20that%20is%20not%20resolved%20please%20open%20a%20support%20ticket%2C%20or%20contact%20GetHelp%20if%20you%20want%20to%20file%20an%20escalation.%20%26nbsp%3B%20%26nbsp%3B%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-642686%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-642686%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20an%20auto%20attendant%20with%20menu%20is%20there%20a%20way%20to%20have%20it%20default%20to%20a%20particular%20menu%20item%20if%20the%20user%20doesn't%20choose%20something.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20you%20have%20reached%20XYZ%20company.%26nbsp%3B%20Press%201%20or%20just%20wait%20to%20continue%20in%20english%20or%20press%202%20to%20continue%20in%20french.%26nbsp%3B%20These%20would%20then%20flip%20to%20the%20appropriate%20AA%20for%20each%20language.%26nbsp%3B%20Just%20as%20an%20example%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-643429%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-643429%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%26nbsp%3Bthe%20service%20is%20broken.%20This%20is%20a%20product%20development%20issue.%20You%20and%20your%20developers%20have%20to%20fix%20this%20mess.%20What%20do%20you%20expect%20the%20support%20team%20to%20do%20other%26nbsp%3B%20than%20act%20as%20a%20punching%20bag%20at%20this%20point%3F%20The%20support%20team%20has%20already%20informed%20me%20about%20the%20proposed%20licensing%20work%20around%20to%20address%20the%20AA%2FCQ%20issues%20as%20most%20people%20have%20detailed%20on%20this%20forum.%20This%20is%20not%20an%20acceptable%20solution.%20This%20is%20more%20than%20an%20inconvenience.%20This%20type%20of%20forced%20improperly%20vetted%20%3CSTRONG%3E%22feature%22%3C%2FSTRONG%3E%20roll%20affects%20end-user%20customers%20and%20partners%20alike.%20What%20is%20it%20going%20to%20take%20to%20make%20Microsoft%20to%20realize%20these%20types%20of%20rushed%20implementations%20cause%20productivity%20and%20monetary%20issues%20for%20customers%20and%20reflect%20negatively%20on%20the%20partners%20that%20sell%2C%20implement%20and%20support%20Microsoft%20products.%20As%20the%20product%20manager%20you%20have%20failed%20us%20and%20this%20community.%20This%20type%20of%20work%20is%20unacceptable%20and%20is%20prime%20example%20of%20everything%20that%20is%20wrong%20with%20cloud%20services%20today.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-644154%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-644154%22%20slang%3D%22en-US%22%3EI%20would%20expect%20at%20the%20very%20least%20that%20the%20migration%20to%20the%20new%20interface%20(from%20old%20UM)%20would%20maintain%20same%20features%20as%20the%20previous%20system.%20With%20UM%2C%20the%20auto%20attendant%20would%20just%20kick%20into%20after%20hours%20mode%20when%20a%20holiday%20is%20scheduled.%20Here's%20a%20link%20to%20the%20documentation%20for%20the%20old%20UM%20auto%20attendant.%20It%20states%20that%20the%20system%20will%20kick%20over%20to%20the%20after%20hours%20business%20system%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fvoice-mail-unified-messaging%2Fautomatically-answer-and-route-calls%2Fcreate-a-holiday-schedule%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fvoice-mail-unified-messaging%2Fautomatically-answer-and-route-calls%2Fcreate-a-holiday-schedule%3C%2FA%3E%20I%20appreciate%20giving%20the%20users%20a%20choice%20(the%20old%20system%20only%20went%20to%20after%20hours)%20but%20I%20find%20it%20hard%20to%20believe%20that%20the%20choices%20provided%20(disconnect%20or%20redirect%20to%20another%20auto%20attendant)%20are%20preferred%20by%20anyone%20over%20the%20original%20after%20hours%20approach.%20As%20it%20is%20now%2C%20the%20system%20is%20unusable%20and%20I%20still%20have%20to%20just%20change%20my%20business%20hours%20and%20greeting%20for%20every%20holiday.%20I%20have%20been%20anxiously%20waiting%20for%20the%20voicemail%20option%20(also%20available%20in%20the%20old%20system)%20because%20I%20have%20had%20to%20create%205%20separate%20accounts%20(consuming%20licenses)%20AND%20setup%20Flow%20tasks%20for%20each%20just%20to%20simulate%20a%20shared%20voicemail%20box.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-644485%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-644485%22%20slang%3D%22en-US%22%3E%3CP%3Ethanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F92230%22%20target%3D%22_blank%22%3E%40Mike%20Dominik%3C%2FA%3E%26nbsp%3B%20for%20the%20feedback%2C%20totally%20agree.%20The%20holiday%20logic%20in%20auto%20attendant%20need%20to%20be%20revisited%2C%20and%20current%20options%20are%20not%20sufficient.%20What%20we%20want%20to%20do%20is%20fix%20the%20logic%20(more%20like%20reverse%20it)%2C%20and%20add%20%3CSTRONG%3EPSTN%20transfer%3C%2FSTRONG%3E%20and%20%3CSTRONG%3EVoicemail%3C%2FSTRONG%3E%20to%20the%20%3CSTRONG%3ETransfer%3C%2FSTRONG%3E%20and%20%3CSTRONG%3EDisconnect%3C%2FSTRONG%3E%20options.%20Can%20you%20elaborate%20more%20please%20on%20this%20statement%20%22%3CSPAN%3E%26nbsp%3BI%20still%20have%20to%20just%20change%20my%20business%20hours%20and%20greeting%20for%20every%20holiday%3C%2FSPAN%3E%22%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-644497%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-644497%22%20slang%3D%22en-US%22%3E%3CP%3EQuestion%20to%20Everyone%3A%20did%20anyone%20have%20to%20go%20through%20the%20process%20in%20the%20blog%20to%20fix%20hybrid%20resource%20accounts%3F%20would%20appreciate%20your%20feedback%20on%20that.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-644534%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-644534%22%20slang%3D%22en-US%22%3ELet's%20take%20this%20weekend%20for%20example.%20We%20are%20closed%20from%205%2F24%20at%203pm%20through%20Monday%20all%20day%20for%20Memorial%20Day.%20We%20want%20to%20play%20a%20special%20message%20(holiday%20greeting)%20and%20then%20roll%20into%20the%20after%20hours%20menu.%20My%20current%20process%20is%20to%20change%20my%20business%20hours%20so%20we%20are%20closed%20during%20that%20period%20of%20time%20and%20then%20replace%20the%20After%20Hours%20greeting%20to%20be%20a%20special%20message.%20On%20Tuesday%2C%20I%20have%20to%20log%20back%20in%2C%20reset%20the%20hours%20and%20put%20the%20greeting%20back%20(I%20have%20forgotten%20to%20do%20this%20before).%20What%20I%20would%20like%20is%20for%20the%20holiday%20setup%20to%20just%20roll%20into%20the%20after%20hours%20so%20I%20don't%20have%20to%20do%20this.%20It%20would%20just%20play%20the%20holiday%20message%20and%20then%20treat%20the%20business%20as%20being%20closed.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-643390%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-643390%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%3CSPAN%3Ethanks%20for%20sharing%20your%20feedback%20on%20the%20community.%20I'm%20running%20into%20the%20issue%2C%20that%20I%20can't%20assign%20available%20phonenumbers%20to%20resourceaccounts.%20I%20was%20able%20to%2C%202%20days%20ago%2C%20but%20yesterday%20I%20can't%20anymore.%20I've%20assigned%20a%20E1%2Bphone%20system%2Bcalling%20plan%20subscription%20to%20the%20resource%20account.%26nbsp%3B%20Any%20idea%20%F0%9F%A4%B7%E2%80%8D%3Amale_sign%3A%3C%2Fimg%3E%20(subsciptions%20assigend%2024%20hours%20ago%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E)Found%20the%20issue%20using%20PowerShell.%20The%20numbers%20I%20have%2C%20seem%20to%20be%20assigned%2C%20but%20can't%20unassign%20them%20(yet).%20Perhaps%20a%20time%20related%20issue.%20I%20will%20check%20it%20after%2024%20hours.%3CBR%20%2F%3E%3CSPAN%3E%3CSTRONG%3E%3CEM%3EFixed%20using%3A%26nbsp%3B%3CSPAN%20class%3D%22hljs-pscommand%22%3ESet-csonlinevoiceapplicationinstance%3C%2FSPAN%3E%3CSPAN%20class%3D%22hljs-parameter%22%3E%20-identity%3C%2FSPAN%3E%3CSPAN%3E%20%3CRESOURCE%20account%3D%22%22%20oid%3D%22%22%3E%3C%2FRESOURCE%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22hljs-parameter%22%3E%20-TelephoneNumber%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22hljs-literal%22%3E%24null%3C%2FSPAN%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-left%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F115920iD8C72E6060A40FF1%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22002.PNG%22%20title%3D%22002.PNG%22%20%2F%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-left%22%20style%3D%22width%3A%20276px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F115919i772ABDC04DC2BCF4%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22001.PNG%22%20title%3D%22001.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-644984%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-644984%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3Esorry%2C%20we%20ar%20cloud%20only%2C%20no%20hybrid.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-645793%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-645793%22%20slang%3D%22en-US%22%3EI%20see%20here%20that%20there%20will%20be%20another%20unwanted%20change%20foisted%20on%20us%20in%20the%20near%20future%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FDeployOffice%2Fteams-install%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FDeployOffice%2Fteams-install%3C%2FA%3E%20Part%20way%20down%20the%20page%20this%20says%20that%20not%20only%20will%20the%20Teams%20client%20be%20part%20of%20*new*%20office%20installs%20(understandable%20and%20easily%20dealt%20with%20by%20excluding%20it)%20but%20that%20you'll%20actually%20be%20quietly%20be%20sneaking%20the%20Teams%20client%20into%20*EXISTING*%20installs%20when%20they're%20updated.%20Unsurprisingly%20the%20doc%20doesn't%20go%20into%20any%20details%20about%20methods%20to%20rerun%20the%20ODT%20%2Fconfigure%20on%20existing%20clients%2C%20nor%20does%20it%20say%20what%20that%20client%20experience%20is%20going%20to%20be%20like.%20Will%20there%20be%20interaction%20required%3F%20Will%20users%20get%20strange%20popups%2Fwarnings%20that%20will%20lead%20to%20helpdesk%20impact%3F%20Will%20they%20be%20unable%20to%20launch%20office%20apps%20while%20this%20update%20is%20occurring%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-648653%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-648653%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3EI%20am%20facing%20issues%20with%20the%20AA%2FCQ%20with%20direct%20routing.%20From%20the%20configuration%20point%20of%20view%20all%20went%20well%20as%20per%20the%20documentation.%26nbsp%3B%20I%20receive%20an%20SIP%20error%20code%20from%20the%20CCE%20(mediation)%20%22480%22%3C%2FP%3E%3CP%3EResource%20Account%20created%20for%20AA%2FCQ%2C%20assigned%20the%20E1%20and%20Phones%20system%20license.%3C%2FP%3E%3CP%3EPhone%20number%20assigned%20using%20Powershell%20for%20direct%20routing%20for%20this%20resource%20account.%3C%2FP%3E%3CP%3EAA%2FCQ%20configured%20to%20use%20the%20repective%20resource%20account.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECalls%20from%20the%20SIP%20trunk%20lands%20on%20the%20SBC%20and%20routed%20to%20CCE%20(Mediation)%2C%20response%20from%20the%20cloud%20back%20via%26nbsp%3Bthe%20CCE%20to%20the%20SBC%20shows%20an%20error%20code%20of%20480%20(temprarily%20unaavailable)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-648706%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-648706%22%20slang%3D%22en-US%22%3E%3CP%3EDirect%20Routing%20only%20works%20with%20Teams.%20CCE%20works%20based%20on%20federation.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-648791%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-648791%22%20slang%3D%22en-US%22%3E%3CDIV%20class%3D%22lia-message-author-with-avatar%22%3E%3CSPAN%20class%3D%22UserName%20lia-user-name%20lia-user-rank-Occasional-Contributor%20lia-component-message-view-widget-author-username%22%3E%40%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F30701%22%20target%3D%22_self%22%3E%3CSPAN%20class%3D%22%22%3EDamian%20Kozlowsk%3C%2FSPAN%3E%3C%2FA%3E%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20class%3D%22lia-message-author-with-avatar%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22lia-message-author-with-avatar%22%3E%3CSPAN%20class%3D%22UserName%20lia-user-name%20lia-user-rank-Occasional-Contributor%20lia-component-message-view-widget-author-username%22%3E%3CSPAN%20class%3D%22%22%3E%26nbsp%3B%3A%20I%20tried%20routing%20this%20call%20via%20Teams%20interface%20now%20and%20now%20receive%20an%20error%20code%20of%20404%20from%20MS%20cloud.%26nbsp%3B%20%26nbsp%3BNot%20sure%20if%20it%20takes%20the%20cloud%20changes%20to%20propogate%20and%20takes%2024%20hours%20or%20it%20is%20some%20other%20kind%20of%20issue.%20%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20class%3D%22lia-message-author-with-avatar%22%3E%26nbsp%3B%3C%2FDIV%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-648799%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-648799%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F115574%22%20target%3D%22_blank%22%3E%40Thangavel%20Mudaliar%3C%2FA%3EI'm%20also%20seeing%20SIP%2F2.0%20480%20Temporarily%20Unavailable%20errors%20in%20relation%20to%20our%20Skype%2FExchange%20hybrid%20environment%2C%20specifically%20Exchange%20Online%20UM.%20We%20have%20a%20group%20of%20people%20using%20Skype%20onprem%20%2B%20Exchange%20Online%20%2B%20Exchange%20Online%20UM%20for%20voicemail%20and%20calls%20are%20consistently%20not%20working%20to%20the%20Outlook%20Voice%20Access%20number%2C%20and%20inconsistently%20not%20timing%20out%20to%20their%20voicemail%20box.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20to%20think%20some%20of%20these%20Exchange%20Online%20UM%20%2B%20Cloud%20Voicemail%20%2B%20Phone%20System%20errors%20are%20related.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-648816%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-648816%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F115574%22%20target%3D%22_blank%22%3E%40Thangavel%20Mudaliar%3C%2FA%3E%20Yeah%20404%20normally%20relates%20to%20replication.%20In%20my%20case%20it%20took%20nearly%203%20days%20before%20it%20kicked%20in.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-651280%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-651280%22%20slang%3D%22en-US%22%3E%3CP%3EHas%20anybody%20tried%20out%20the%20new%20feature%20%3A%20%22A%3CSPAN%3Essign%20a%20%3C%2FSPAN%3E%3CSTRONG%3Ehybrid%20number%3C%2FSTRONG%3E%3CSPAN%3E%20to%20AA%2FCQ%20(in%20public%20preview)%22%20%3F%20I%20have%20trying%20to%20create%20an%20on-premise%20resource%20account%20via%20the%20cmdlet%20%22New-CsHybridApplicationEndPoint%22.%20We%20clearly%20see%20that%20the%20account%20is%20created%20in%20Office365%2C%20but%20can't%20assign%20it%20to%20a%20AA%2FCQ%2C%20as%20we%20can%20only%20assign%20Cloud%20Resource%20Accounts%20to%20a%20AA%2FCQ.%20We%20are%20stuck%20at%20the%20moment%20as%20we%20can't%20create%20anymore%20AA%2FCA%20in%20our%20Skype%20for%20Business%202015%20Hybrid%20environment.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-652405%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-652405%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F191273%22%20target%3D%22_blank%22%3E%40Philip%20De%20Graef%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20not%20been%20able%20to%20do%20this%20either.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESteps%20I%20took%3A%3C%2FP%3E%3CP%3E1.%20Online%20powershell%20ran%20new-csonlineapplicationendpoint%3C%2FP%3E%3CP%3E2.%20On-premises%20powershell%20ran%20new-cshybridapplicationendpoint%20per%20the%20output%20of%20%231%3C%2FP%3E%3CP%3E3.%20Assigned%20the%20on-premises%20endpoint%20a%20DID%20number%20using%20set-csybridapplicationendpoint%20in%20on-premises%20powershell%3C%2FP%3E%3CP%3E4.%20After%20AD%20Sync%20assigned%20the%20account%20phone%20system%2C%20teams%2C%20and%20skype%20for%20business%20license%3C%2FP%3E%3CP%3E5.%20Resource%20account%20shows%20up%20under%20Teams%20Admin%20Portal%20under%20Org%20Wide%20Settings-%26gt%3BResource%20accounts%3C%2FP%3E%3CP%3E6.%20Within%20the%20call%20queue%20go%20to%20assign%20a%20resource%20account%20and%20it%20does%20not%20show%20up%20so..%3C%2FP%3E%3CP%3E7.%20Go%20to%20the%20resource%20account%20and%20under%20Assign%2FUnassign%20I'm%20able%20to%20assign%20it%20to%20a%20call%20queue%20there%3C%2FP%3E%3CP%3E8.%20Go%20back%20to%20call%20queue%20and%20see%20the%20resource%20account%20is%20assigned%20-%20wait%20some%20time%20for%20replication%3C%2FP%3E%3CP%3E9.%20Call%20the%20number%20-%20all%20I%20get%20is%20ringing%20and%20on-premises%20shows%20nothing%20in%20the%20trace%20logs.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-654540%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-654540%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%26nbsp%3BCall%20Queues%20and%20auto%20attendant%20management%20is%20down%20again....%20Reopened%20case%26nbsp%3B%3CSPAN%3E14334892%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fadmin1e.online.lync.com%2FOcsPowershellWebservice%2FService.svc%2FV1_AutoAttendant%3FFirst%3D20%26amp%3BIncludeStatus%3Dtrue%26amp%3BadminDomain%3D%26lt%3Bdomainname%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fadmin1e.online.lync.com%2FOcsPowershellWebservice%2FService.svc%2FV1_AutoAttendant%3FFirst%3D20%26amp%3BIncludeStatus%3Dtrue%26amp%3BadminDomain%3D%3CDOMAINNAME%3E%3C%2FDOMAINNAME%3E%3C%2FA%3E%26gt%3B%20HTTP%2F1.1%20Host%3A%20admin1e.online.lync.com%20HTTP%20Error%20503.%20The%20service%20is%20unavailable.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-658016%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-658016%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%3A%20I%20am%20trying%20to%20redirect%20my%20call%20from%20Auto%20Attendant%20to%20a%20Call%20Queue.%20The%20Call%20Queue%20is%20created%20and%20I%20have%20added%20a%20Resource%20Account%20for%20both%20CQ%20and%20AA.%20But%20when%20I%20trying%20to%20find%20the%20CQ%20from%20Voice%20App%20list%20its%20not%20showing.%20I%20tried%20to%20add%20the%20Resource%20Account%20instead%20which%20is%20searchable%20but%20when%20I%20am%20submitting%20its%20giving%20me%20a%20error%20%22Error%20We%20can't%20create%20call%20handler%20at%20the%20moment.%22%20Can%20you%20please%20let%20me%20know%20how%20we%20can%20do%20the%20redirection%20from%20a%20AA%20to%20a%20CQ.%20Thanks%20Avijit%20Chakraborty%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-658079%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-658079%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20been%20eagerly%20awaiting%20the%20Call%20Queue%20and%20Auto%20Attendant%20feature%20in%20Teams%20for%20probably%20well%20over%20a%20year%20as%20I%20have%20had%20customers%20working%20with%20'post-it%20notes'%20on%20their%20Polycom%20VVX%20phones%20to%20allow%20them%20to%20identify%20incoming%20calls%20to%20queue%20calls%20as%20the%20TOAST%20showed%20only%20the%20GUID%20(according%20to%20MS%20it%20wasn't%20worth%20fixing%20in%20SfB%20and%20will%20be%20in%20Teams).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%20however%20I%20can't%20even%20seems%20to%20associate%20a%20number%20with%20said%20CQ%20or%20AA%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20this%20stuff%20in%20anyway%20get%20a%20quality%20and%2For%20even%20a%20basic%20functionality%20check%20before%20passing%20out%20into%20production%3F%20What's%20the%20most%20irritating%20is%20that%20none%20of%20this%20seems%20to%20be%20communicated%20-%20indeed%20the%20title%20of%20this%20post%20'%3CSPAN%3EThe%20service%20updates%20for%20Auto%20Attendant%20and%20Call%20Queues%20were%20completed%20successfully%20this%20week'%20but%20no-where%20does%20it%20then%20go%20on%20to%20say%20-%20apart%20from%20the%20most%20basic%20part%20of%20setting%20up%20a%20call%20queue%20(as%20in%20giving%20it%20a%20number)%20doesn't%20actually%20work!%3F!%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20have%20raised%20tickets%20-%20always%20to%20no%20avail.%20I'm%20getting%20a%20bit%20fed%20up%20of%20looking%20the%20plonker%20here%20-%20and%20the%20good%20old%20trusted%20PBX%20in%20the%20corner%20might%20have%20to%20be%20dusted%20off%20and%20brought%20back%20into%20play.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-658088%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-658088%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20totally%20unacceptable%2C%20I%20have%20just%20started%20work%20to%20move%20our%20entire%20organisation%20to%20the%20cloud%20PBX%20system%20but%20now%20through%20the%20rollout%20of%20a%20new%20user%20interface%20you%20require%20us%20to%20purchase%20licences%20for%20Auto%20Attendants%20until%20you%20fix%20the%20problem%20you%20have%20created%3F%20In%20that%20case%20are%20you%20going%20to%20refund%20us%20for%20the%20additional%20licences%20we%20now%20'temporarily'%20require%20while%20you%20fix%20this%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAt%20the%20moment%20we%20have%20halted%20our%20migration%20until%20this%20is%20resolved.%20I%20have%20raised%20a%20support%20ticket%2C%20but%20I%20know%20they%20are%20unlikely%20to%20be%20able%20to%20help%20at%20this%20point.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-658110%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-658110%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%26nbsp%3BAny%20idea%20when%20we%20will%20see%20some%20respite%20from%20this%20train%20wreck%20of%20a%20%22FeaTuRe%20UpDate%22%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-658839%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-658839%22%20slang%3D%22en-US%22%3E%3CP%3EI%20hope%20this%20helps%20everyone%20in%20this%20post%20including%20Michael%20above.%26nbsp%3B%20We%20went%20through%20the%20exact%20same%20thing%2C%20ported%20our%20only%20number%20required%20the%20weekend%20of%20the%20original%20AA%20and%20Call%20Queue%20Migration%20and%20still%20do%20not%20have%20proper%20control%20over%20service%20numbers%20in%20teams%20portal%20and%20it%20is%20gone%20in%20Legacy%20portal.%26nbsp%3B%20The%20fix%20for%20us%20ended%20up%20being%20a%20simple%20thing%20but%20hard%20to%20find%2C%20since%20all%20our%20resource%20accounts%2C%20AA%2C%20and%20Call%20queues%20were%20already%20done%20when%20MS%20did%20migration.%26nbsp%3B%20The%20fix%20is%20simply%20do%20not%20use%20exisiting%20resource%20accounts%20and%20all%20commands%20have%20to%20be%20done%20in%20Powershell%20that%20is%20documented%20in%20MS%20article.%26nbsp%3B%20So%20make%20new%20resource%20account%20in%20powershell%2C%20assign%20licenses%20to%20the%20resource%20account%2C%20then%20assign%20number%20to%20resource%20account%20in%20powershell.%26nbsp%3B%20then%20you%20can%20assign%20the%20resource%20account%20to%20your%20auto%20attendant%20in%20teams%20admin%20portal.%26nbsp%3B%20Below%20is%20the%20article%20that%20has%20all%20the%20required%20commands.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fmanage-resource-accounts%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fmanage-resource-accounts%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%20class%3D%22lia-message-author-with-avatar%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22lia-message-author-with-avatar%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-658791%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-658791%22%20slang%3D%22en-US%22%3E%3CP%3EUPDATE%3A%2005%2F30%2F19%20-%201%3A42PM%20EST%20-%20Port%20team%20(ptn%40microsoft.com)%20just%20emailed%20me%20back%20per%20an%20email%20I%20sent%20to%20them%20earlier%20today.%26nbsp%3B%20I%20requested%20the%20main%20%22published%22%20telephone%20number%20be%20converted%20from%20a%20%22service%22%20number%20back%20to%20a%20%22user%22%20number.%26nbsp%3B%20Logged%20into%20the%20Teams%20Admin%20Center%20and%20clicked%20on%20the%20Legacy%20Portal%20and%20was%20able%20to%20successfully%20assign%20the%20number%20to%20one%20of%20our%20end%20users.%26nbsp%3B%20We%20now%20at%20least%20have%20one%20phone%20set%20ringing%20in%20with%20our%20main%20%22published%22%20telephone%20number.%26nbsp%3B%20Decent%20temporary%20Band-aid.%26nbsp%3B%20Would%20have%20done%20that%20days%20ago%20had%20support%20tech%20known%20of%20such%20problem%20existed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3EI've%20stumbled%20upon%20this%20thread%20today%20while%20searching%20for%20a%20fix%20for%20a%20client%20who%20has%20now%20been%20without%20inbound%20phone%20service%20on%20their%20main%20%22published%22%20telephone%20number%20for%20%2B48%20hours.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20built%20out%20their%20%22Phone%20System%22%20several%20weeks%20ago%3B%20assigned%20users%20numbers%2C%20reconfigured%20phones%20on%20all%20desks%2C%20got%20them%20outfitted%20with%20dial%20tone%2C%20built%20out%20their%20auto%20attendant%20with%20a%20temporary%20service%20number%20assigned%2C%20etc.%26nbsp%3B%20We%20then%20contacted%20their%20existing%20carrier%20to%20forward%20their%20main%20%22published%22%20telephone%20number%20to%20the%20temporary%20number%20we%20had%20assigned%20to%20the%20auto%20attendant.%26nbsp%3B%20Everything%20went%20great.%26nbsp%3B%20Had%20them%20migrated%20to%20Microsoft%20and%20fully%20operational%20in%20a%20matter%20of%20hours%20with%20no%20downtime.%26nbsp%3B%20We%20then%20placed%20our%20port%20order%20on%2005%2F21%2F19%20for%20their%20main%20%22published%22%20telephone%20number%2C%20which%20happened%20to%20be%20the%20only%20telephone%20number%20we%20needed%20from%20their%20existing%20carrier%20since%20it%20was%20the%20only%20%22published%22%20telephone%20number%20for%20this%20business.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETuesday%20morning%2C%2005%2F28%2F19%2C%20as%20scheduled%2C%20their%20main%20%22published%22%20telephone%20number%20ported%20to%20Microsoft.%26nbsp%3B%20Based%20on%20everything%20discussed%20in%20this%20entire%20thread%2C%20what%20do%20you%20think%20happened%20next%3F%3F%3F%3F%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYep!%26nbsp%3B%20Microsoft%20now%20has%20possession%20of%20our%20client's%20%22ONLY%22%20and%20main%20%22PUBLISHED%22%20telephone%20number%20and%20it%20can't%20be%20assigned%20to%20not%20only%20the%20auto%20attendant%20we%20created%2C%20but%20ANY%20auto%20attendant%20or%20call%20queue%20we%20try%20to%20build.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20personally%20worked%20with%20support%20for%20almost%2048%20hours%20and%20they've%20been%20able%20to%20fix%20nothing%2C%20nor%20did%20they%20bother%20to%20even%20elude%20to%20any%20such%20known%20issue%20(internal%20communication%20problem%20inside%20Microsoft%20or%20stall%20tactic%3F).%26nbsp%3B%20Instead%20they've%20spun%20my%20wheels%20for%202%20days.%26nbsp%3B%20This%20morning%2C%20our%20client%20started%20day%203%20of%20the%20work%20week%20with%20still%20no%20inbound%20calling%20to%20their%20main%20%22published%22%20telephone%20number%20with%20inbound%20callers%20being%20told%20the%20number%20is%20%22NOT%20IN%20SERVICE!%22%26nbsp%3B%20They%20are%20essentially%20on%20day%203%20of%20no%20business...and%20my%20company%20looks%20like%20a%20bunch%20of%20A**HOLES%20since%20it%20was%20our%20brilliant%20idea%20to%20migrate%20them%20to%20Microsoft.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBefore%2C%20during%20and%20after%20the%20port%2C%20there%20was%20NEVER%20any%20disclaimer%20that%20stated%20in%20ANY%20way%20that%20in%20the%20event%20we%20were%20an%20organization%20attempting%20to%20port%20in%20numbers%20that%20would%20be%20designated%20as%20service%20numbers%2C%20that%20were%20to%20be%20assigned%20to%20necessary%20account%20objects%2C%20that%20there%20would%20be%20ANY%20issue%20in%20doing%20such.%26nbsp%3B%20HOWEVER%2C%20this%20thread%20is%20over%202%20weeks%20old%20and%20there%20appears%20to%20still%20be%20no%20resolution%20in%20sight.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%26nbsp%3B%20What%20is%20the%20fix%20for%20our%20client...what%20is%20the%20time%20table%20to%20resolution%3F%26nbsp%3B%20Do%20we%20place%20another%20port%20order%20with%20another%20carrier%20to%20temporarily%20port%20the%20number%20away%20from%20Microsoft%20so%20they%20can%20forward%20it%20to%20one%20of%20our%20end-user's%20user%20numbers%3F%26nbsp%3B%20We%20need%20a%20fix%20yesterday%20and%20support%20is%20dragging%20their%20butts%20on%20providing%20one.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2.%20Why%20in%20God's%20name%20were%20we%20not%20warned%20of%20the%20problem%20by%20the%20port%20team%20BEFORE%2C%20DURING%20or%20AFTER%20the%20port%20order%20was%20placed%3F%26nbsp%3B%20This%20issue%20is%20weeks%20old.%26nbsp%3B%20If%20there%20is%20such%20a%20known%20problem%2C%20why%20has%20the%20port%20team%20not%20put%20a%20halt%20or%20disclaimer%20on%20porting%20service%20numbers%20in%20from%20other%20carriers%3F%26nbsp%3B%20You%20are%20essentially%20dismantling%20and%20handcuffing%20clients%20in%20such%20scenarios%20as%20I%20have%20described.%26nbsp%3B%20If%20by%20chance%20you're%20still%20porting%20in%20(service)%20numbers%20from%20other%20carriers%20that%20need%20to%20be%20assigned%2C%20STOP%20IT!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20write%20back%20providing%20a%20reasonable%20pathway%20to%20resolution.%26nbsp%3B%20Our%20client%20needs%20to%20be%20back%20in%20business.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMichael%20Lawrence%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-659651%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-659651%22%20slang%3D%22en-US%22%3E%3CP%3EDays%20in%20and%20still%20unable%20to%20get%20key%20presses%20working%20on%20our%20new%20AA.%26nbsp%3B%20Pathetic.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-659836%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-659836%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3E%22What%20to%20expect%20after%20the%20service%20update%3F%3C%2FSTRONG%3E%3C%2FP%3E%3CUL%3E%3CLI%3EYou%20can%20now%20create%20auto%20attendants%20and%20call%20queues%20in%20Teams%20Admin%20Portal%3C%2FLI%3E%3CLI%3EYour%20previous%20auto%20attendants%20and%20call%20queues%20were%20migrated%20to%20Teams%20Admin%20portal%2C%20and%20they%20should%20%3CFONT%20color%3D%22%23ff0000%22%3E%3CSTRONG%3Econtinue%20to%20work%20like%20before%3C%2FSTRONG%3E%22%3C%2FFONT%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%3CFONT%20color%3D%22%23000000%22%3EUnless%20you%20need%20to%20make%20a%20change%20like%20change%20a%20number%20on%20an%20Auto-Attendant.%20Then%20you%20have%20to%20license%2Fpay%20up%20until%20the%20hopeful%20July%20free%20licensing%20if%20you%20want%20to%20save%20the%20change.%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%20color%3D%22%23000000%22%3EFor%20the%20sake%20of%20two%20months%20of%20new%20features%20could%20this%20have%20been%20delayed%20(and%20tested%20and%20refine%20a%20little%20more)%20two%20months%20and%20scheduled%20at%20the%20same%20time%3F%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-660440%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-660440%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F336185%22%20target%3D%22_blank%22%3E%40Robert_Hurd%3C%2FA%3E%26nbsp%3Bthanks%20for%20the%20tip%20however%20in%20my%20case%20I%20get%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESet-CsOnlineVoiceApplicationInstance%20-Identity%20name%40mydomain.com%20-TelephoneNumber%20%2Bmyservicenumber%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWARNING%3A%20The%20following%20Application%20Instance%20not%20present%20in%20BVD%3A%20%5Bstring%5D%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-660463%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-660463%22%20slang%3D%22en-US%22%3E%3CP%3EAn%20update%20from%20Microsoft%20support%20regarding%20the%20Auto%20Attendant%20Licencing%20'requirements'%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThey%20explained%20to%20me%20that%20they%20have%20received%20many%20complaints%20about%20the%20issue%20but%20are%20powerless%20to%20do%20anything%20to%20help%20(as%20I%20guessed).%20They%20agree%20that%20from%20a%20customer%20point%20of%20view%20what%20has%20happened%20here%20is%20very%20poor%20and%20encourage%20us%20to%20make%20our%20views%20clear%20on%20the%20user%20voice%20website.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThey%20also%20encouraged%20me%20to%20share%20the%20following%20link%20and%20get%20anyone%20in%20the%20same%20position%20to%20vote%20and%20comment%20to%20move%20it%20up%20their%20priority%20lists...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fmicrosoftteams.uservoice.com%2Fforums%2F555103-public%2Fsuggestions%2F37694869-call-queue-and-auto-attendant-resource-licensing%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmicrosoftteams.uservoice.com%2Fforums%2F555103-public%2Fsuggestions%2F37694869-call-queue-and-auto-attendant-resource-licensing%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-660539%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-660539%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%26nbsp%3Ban%20update%20would%20be%20nice.%20Also%20who%20do%20you%20report%20to%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-660735%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-660735%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F86946%22%20target%3D%22_blank%22%3E%40Paul%20Coward%3C%2FA%3E%26nbsp%3B%20did%20you%20create%20the%20resource%20account%20by%20using%20the%26nbsp%3B%3C%2FP%3E%3CP%3ENew-CsOnlineApplicationInstance%20-UserPrincipalName%20testra1%40contoso.com%20-ApplicationId%20%E2%80%9Cce933385-9390-45d1-9512-c8d228074e07%E2%80%9D%20-DisplayName%20%22Resource%20account%201%22%3C%2FP%3E%3CP%3ECommand%3F%26nbsp%3B%20I%20was%20getting%20exactly%20the%20same%20thing%20until%20i%20i%20created%20the%20new%20resource%20account%20within%20powershell.%26nbsp%3B%20I%20am%20guessing%20this%20is%20what%20you%20have%20tried%20and%20it%20has%20just%20broken%20more%20for%20people%20since%20the%20may%2005%20weekend%20when%20this%20all%20started.%26nbsp%3B%20Let%20me%20know%20and.i%20will%20help%20how%20i%20can.%26nbsp%3B%20I%20really%20hope%20you%20have%20not%20tried%20this%20and%20this%20works%20for%20you.%26nbsp%3B%20I%20am%20also%20amazed%20how%20this%20has%20gone%20and%20i%20at%20least%20hope%20Ms%20learns%20from%20this%20as%20Thia%20has%20been%20handled%20and%20communicated%20very%20poorly.%26nbsp%3B%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F86946%22%20target%3D%22_blank%22%3E%40Paul%20Coward%3C%2FA%3E%26nbsp%3Bdid%20you%20assign%20the%20calling%20plan%20and%20communication%20credit%20license%20after%20you%20create%20resource%20account%3F%3C%2FP%3E%3CP%3EThe%20application%20ID's%20that%20you%20need%20to%20use%20while%20creating%20the%20application%20instances%20are%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAuto%20Attendant%3A%20ce933385-9390-45d1-9512-c8d228074e07%3C%2FP%3E%3CP%3ECall%20Queue%3A%2011cd3e2e-fccb-42ad-ad00-878b93575e07%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-662583%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-662583%22%20slang%3D%22en-US%22%3E%3CP%3EUsing%20%3CSTRONG%3ECommon%20Area%20Phone%3C%2FSTRONG%3E%20License%20bundle%20%2B%20a%20%3CSTRONG%3ECall%20plan%3C%2FSTRONG%3E%2C%20to%20license%20a%20AA%2FCQ%20resource%20account%20requiring%20PSTN%20number%20assignment%2C%20seems%20to%20work%20and%20be%20cheaper%20than%20E1%20%2B%20call%20plan.%3CBR%20%2F%3ENote%20sure%20why%20Microsoft%20doco%20doesn't%20suggest%20that%20in%20interim%20until%20they%20have%20new%20AA%2FCQ%20Licensing%20released%20in%20July%20(hopefully%20sooner%20not%20later).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20note%2C%20that%20assigning%20multiple%20numbers%20to%20a%20single%20Auto-Attendant%2FCall-Queue%20is%20done%20by%20assigning%20each%20number%20to%20a%20single%20resource%20account%2C%20which%20are%20then%20assigned%20to%20an%20AA%2FCQ%2C%20each%20resource%20account%20will%3CSPAN%3E%20need%20to%20be%20licensed%3C%2FSPAN%3E%20at%20this%20stage%20.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-662584%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-662584%22%20slang%3D%22en-US%22%3E%3CP%3EHad%20an%20issue%20where%20an%20auto-attendant%20that%20was%20migrated%20to%20Teams%20portal%20needed%20it's%20number%20changed.%20So%20I%20had%20to%20license%20the%20resource%20account%20to%20be%20enabled%20to%20list%20and%20assign%20the%20desired%20PSTN%20number%2C%20it%20would%20save%20it%20saved%20successfully%20and%20display%20in%20list%20correctly%2C%20but%20not%20work.%20after%20checking%20the%20number%20in%20SfB%20portal%20I%20noticed%20the%20number%20was%20listed%20but%20not%20assigned.%20going%20back%20to%20teams%20portal%20window%20and%20refreshing%20resource%20accounts%20list%2C%20the%20list%20would%20then%20reveal%20that%20the%20PSTN%20number%20assignment%20had%20reverted%20back%20to%20original%20PSTN%20number.%20Tried%20same%20process%20again%20with%20same%20result.%20I%20had%20to%20create%20a%20new%20resource%20account%2C%20transfer%20licenses%20to%20successfully%20update%20the%20AA%20PSTN%20number.%20So%20another%20GUI%20bug%20for%20the%20Teams%20team%20to%20resolve.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-665367%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-665367%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F36671%22%20target%3D%22_blank%22%3E%40Wes%20Lazara%3C%2FA%3E%20-%20I'm%20following%20up%20on%20your%20post%20from%20May%2024%2C%20about%20Microsoft%20Teams%20coming%20to%20existing%20installations%20of%20Office%20365%20ProPlus%2C%20and%20am%20happy%20to%20address%20your%20concerns.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20%23f8f8f8%3B%20color%3A%20%23333333%3B%20font-family%3A%20'SegoeUI'%2C'Lato'%2C'Helvetica%20Neue'%2CHelvetica%2CArial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20line-height%3A%201.7142%3B%20orphans%3A%202%3B%20overflow-wrap%3A%20break-word%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3EPart%20way%20down%20the%20page%20this%20says%20that%20not%20only%20will%20the%20Teams%20client%20be%20part%20of%20*new*%20office%20installs%20(understandable%20and%20easily%20dealt%20with%20by%20excluding%20it)%20but%20that%20you'll%20actually%20be%20quietly%20be%20sneaking%20the%20Teams%20client%20into%20*EXISTING*%20installs%20when%20they're%20updated.%3CBR%20%2F%3E%3CEM%3E%3CSPAN%20style%3D%22text-align%3A%20left%3B%20color%3A%20%23333333%3B%20text-transform%3A%20none%3B%20line-height%3A%201.7142%3B%20text-indent%3A%200px%3B%20letter-spacing%3A%20normal%3B%20font-family%3A%20inherit%3B%20font-size%3A%2016px%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20text-decoration%3A%20none%3B%20word-spacing%3A%200px%3B%20display%3A%20inline%20!important%3B%20white-space%3A%20normal%3B%20cursor%3A%20text%3B%20orphans%3A%202%3B%20float%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20background-color%3A%20%23ffffff%3B%22%3EWe%20posted%20this%20to%20the%20Message%20Center%2C%20as%20well%20as%20the%26nbsp%3B%3CA%20style%3D%22background-color%3A%20transparent%3B%20box-sizing%3A%20border-box%3B%20color%3A%20%23146cac%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20underline%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Froadmap%3Ffilters%3D%26amp%3Bsearchterms%3D51452%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMicrosoft%20365%20Roadmap%3C%2FA%3E%2C%20but%20posting%20about%20it%20here%2C%20as%20you've%20done%2C%20is%20another%20great%20way%20to%20inform%20people.%26nbsp%3B%20Thank%20you!%3C%2FSPAN%3E%3C%2FEM%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20%23f8f8f8%3B%20color%3A%20%23333333%3B%20font-family%3A%20'SegoeUI'%2C'Lato'%2C'Helvetica%20Neue'%2CHelvetica%2CArial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20line-height%3A%201.7142%3B%20orphans%3A%202%3B%20overflow-wrap%3A%20break-word%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3EUnsurprisingly%20the%20doc%20doesn't%20go%20into%20any%20details%20about%20methods%20to%20rerun%20the%20ODT%20%2Fconfigure%20on%20existing%20clients%2C%20nor%20does%20it%20say%20what%20that%20client%20experience%20is%20going%20to%20be%20like.%3CSPAN%20style%3D%22background-color%3A%20%23f8f8f8%3B%20box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20display%3A%20inline%3B%20float%3A%20none%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20line-height%3A%201.7142%3B%20orphans%3A%202%3B%20overflow-wrap%3A%20break-word%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3E%3CSPAN%20style%3D%22background-color%3A%20%23ffffff%3B%20box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20cursor%3A%20text%3B%20display%3A%20inline%3B%20float%3A%20none%3B%20font-family%3A%20inherit%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20line-height%3A%201.7142%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3E%26nbsp%3B%20%3CEM%3EIn%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FDeployOffice%2Fteams-install%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EDocs.Microsoft.Com%20article%3C%2FA%3E%20you%20mentioned%20above%2C%20about%20halfway%20down%20the%20page%2C%20is%20this%20information%20about%20running%20ODT%20in%20the%20%2Fconfigure%20mode%20to%20exclude%20the%20Teams%20app%20from%20installing%20on%20computers%20that%20already%20have%20Office%20365%20ProPlus%20installed%20-%20we%20could%20probably%20add%20an%20anchor%20to%20that%20part%20of%20the%20documentation%2C%20to%20make%20it%20easier%20to%20find%20and%20link%20to%3A%3C%2FEM%3E%20%22%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20%23ffffff%3B%20color%3A%20%23000000%3B%20font-family%3A%20Segoe%20UI%2CSegoeUI%2CSegoe%20WP%2CHelvetica%20Neue%2CHelvetica%2CTahoma%2CArial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20400%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3EIf%20you%20don't%20want%20Teams%20to%20be%20added%20to%20%3C%2FSPAN%3E%3CEM%20style%3D%22box-sizing%3A%20inherit%3B%20color%3A%20%23000000%3B%20font-family%3A%20Segoe%20UI%2CSegoeUI%2CSegoe%20WP%2CHelvetica%20Neue%2CHelvetica%2CTahoma%2CArial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20italic%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20400%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3E%3CSTRONG%20style%3D%22box-sizing%3A%20inherit%3B%20font-weight%3A%20600%3B%22%3Eexisting%3C%2FSTRONG%3E%3C%2FEM%3E%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20%23ffffff%3B%20color%3A%20%23000000%3B%20font-family%3A%20Segoe%20UI%2CSegoeUI%2CSegoe%20WP%2CHelvetica%20Neue%2CHelvetica%2CTahoma%2CArial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20400%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3E%20installations%20of%20Office%20365%20ProPlus%20when%20you%20update%20to%20a%20new%20version%2C%20use%20the%20Office%20Deployment%20Tool%20and%20the%20following%20configuration.xml.%20You%20need%20to%20run%20the%20%3C%2FSPAN%3E%3CA%20style%3D%22background-color%3A%20transparent%3B%20box-sizing%3A%20inherit%3B%20color%3A%20var(--primary-base)%3B%20cursor%3A%20pointer%3B%20font-family%3A%20Segoe%20UI%2CSegoeUI%2CSegoe%20WP%2CHelvetica%20Neue%2CHelvetica%2CTahoma%2CArial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20400%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20outline-color%3A%20invert%3B%20outline-style%3A%20none%3B%20outline-width%3A%200px%3B%20overflow-wrap%3A%20break-word%3B%20text-align%3A%20left%3B%20text-decoration%3A%20underline%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FDeployOffice%2Foverview-of-the-office-2016-deployment-tool%22%20data-linktype%3D%22relative-path%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EOffice%20Deployment%20Tool%3C%2FA%3E%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20%23ffffff%3B%20color%3A%20%23000000%3B%20font-family%3A%20Segoe%20UI%2CSegoeUI%2CSegoe%20WP%2CHelvetica%20Neue%2CHelvetica%2CTahoma%2CArial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20400%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3E%20in%20%2Fconfigure%20mode%20on%20each%20device%20before%20you%20update%20to%20the%20new%20version.%3C%2FSPAN%3E%22%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20%23f8f8f8%3B%20color%3A%20%23333333%3B%20font-family%3A%20'SegoeUI'%2C'Lato'%2C'Helvetica%20Neue'%2CHelvetica%2CArial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20line-height%3A%201.7142%3B%20orphans%3A%202%3B%20overflow-wrap%3A%20break-word%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3EWill%20there%20be%20interaction%20required%3F%20Will%20users%20get%20strange%20popups%2Fwarnings%20that%20will%20lead%20to%20helpdesk%20impact%3F%20Will%20they%20be%20unable%20to%20launch%20office%20apps%20while%20this%20update%20is%20occurring%3F%20%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20%23f8f8f8%3B%20color%3A%20%23333333%3B%20font-family%3A%20'SegoeUI'%2C'Lato'%2C'Helvetica%20Neue'%2CHelvetica%2CArial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20line-height%3A%201.7142%3B%20orphans%3A%202%3B%20overflow-wrap%3A%20break-word%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3E%3CSPAN%20style%3D%22background-color%3A%20%23f8f8f8%3B%20box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20display%3A%20inline%3B%20float%3A%20none%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20line-height%3A%201.7142%3B%20orphans%3A%202%3B%20overflow-wrap%3A%20break-word%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3E%3CEM%20style%3D%22box-sizing%3A%20border-box%3B%22%3E%3CSPAN%20style%3D%22background-color%3A%20%23ffffff%3B%20box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20cursor%3A%20text%3B%20display%3A%20inline%3B%20float%3A%20none%3B%20font-family%3A%20inherit%3B%20font-size%3A%2016px%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20line-height%3A%201.7142%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3EThose%20are%20great%20questions.%26nbsp%3B%20The%20Teams%20desktop%20app%20will%20install%20as%20part%20of%20an%20Office%20365%20ProPlus%20update%2C%20so%20the%20experience%20doesn't%20vary%20from%20that.%26nbsp%3B%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FDeployOffice%2Fend-user-update-notifications-for-office-365-proplus%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EThis%20article%3C%2FA%3E%20describes%20the%20end-user%20experience%20for%20Office%20365%20ProPlus%20updates%2C%20and%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FDeployOffice%2Foverview-of-the-update-process-for-office-365-proplus%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ethis%20article%3C%2FA%3E%20provides%20an%20overview%20of%20the%20update%20process.%3C%2FSPAN%3E%3C%2FEM%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20%23f8f8f8%3B%20color%3A%20%23333333%3B%20font-family%3A%20'SegoeUI'%2C'Lato'%2C'Helvetica%20Neue'%2CHelvetica%2CArial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20line-height%3A%201.7142%3B%20orphans%3A%202%3B%20overflow-wrap%3A%20break-word%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3E%3CSPAN%20style%3D%22background-color%3A%20%23f8f8f8%3B%20box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20display%3A%20inline%3B%20float%3A%20none%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20line-height%3A%201.7142%3B%20orphans%3A%202%3B%20overflow-wrap%3A%20break-word%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3E%3CSPAN%20style%3D%22background-color%3A%20%23ffffff%3B%20box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20cursor%3A%20text%3B%20display%3A%20inline%3B%20float%3A%20none%3B%20font-family%3A%20inherit%3B%20font-size%3A%2016px%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20line-height%3A%201.7142%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3EThanks%20again%20for%20your%20feedback%2C%20and%20I%20hope%20you%20find%20the%20information%20in%20this%20response%20helpful.%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20%23f8f8f8%3B%20color%3A%20%23333333%3B%20font-family%3A%20'SegoeUI'%2C'Lato'%2C'Helvetica%20Neue'%2CHelvetica%2CArial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20line-height%3A%201.7142%3B%20orphans%3A%202%3B%20overflow-wrap%3A%20break-word%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3E%3CSPAN%20style%3D%22background-color%3A%20%23f8f8f8%3B%20box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20display%3A%20inline%3B%20float%3A%20none%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20line-height%3A%201.7142%3B%20orphans%3A%202%3B%20overflow-wrap%3A%20break-word%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3E%3CSPAN%20style%3D%22background-color%3A%20%23ffffff%3B%20box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20cursor%3A%20text%3B%20display%3A%20inline%3B%20float%3A%20none%3B%20font-family%3A%20inherit%3B%20font-size%3A%2016px%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20line-height%3A%201.7142%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3ESteve%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-665377%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-665377%22%20slang%3D%22en-US%22%3E%3CP%3EHey%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F8856%22%20target%3D%22_blank%22%3E%40Steve%20Conn%3C%2FA%3E%26nbsp%3B%20%2C%20thank%20you%20for%20the%20update!%26nbsp%3B%20What%20you've%20already%20mentioned%20here%20is%20helpful%20and%20I%20think%20the%20doc%20updates%20you%20suggest%20would%20be%20welcome.%26nbsp%3B%20As%20for%20the%20question%20about%20interaction%2Fpopups%2Fwarning%2Fetc%2C%20I%20was%20referring%20not%20to%20the%20typical%20behind-the-scenes%20update%20process%20during%20which%20Teams%20will%20roll%20out...%26nbsp%3B%20but%20rather%20we%20are%20focused%20on%20preventing%20Teams%20(for%20now%20at%20least)%20from%20rolling%20out%20to%20our%20hundreds%20of%20already-deployed%20c2r%20proplus%20machines.%26nbsp%3B%20What%20mechanism%20is%20suggested%2Fbest%20practice%20to%20actually%20carry%20out%26nbsp%3B%3CSPAN%3E%22%3C%2FSPAN%3E%3CSPAN%3Ethe%20ODT%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3Bin%20%2Fconfigure%20mode%20on%20each%20device%20before%20you%20update%20to%20the%20new%20version%22%20%3F%26nbsp%3B%20And%20does%20that%20suggested%20mechanism%20cause%2Frequire%20interaction%2Fpopups%2Fwarnings%20etc%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThank%20you!%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-665524%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-665524%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F88200%22%20target%3D%22_blank%22%3E%40Jef%20Vleugels%3C%2FA%3E%26nbsp%3Bseems%20like%20you're%20having%20a%20problem%20with%20the%20admin%20portal%2C%20if%20the%20ticket%20is%20open%20the%20portal%20team%20will%20track%20that%20with%20you.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-665528%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-665528%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F351876%22%20target%3D%22_blank%22%3E%40Avijit_Chakraborty%3C%2FA%3E%26nbsp%3B%20you%20currently%20search%20and%20redirect%20calls%20to%20a%20resource%20account%20instead%20of%20a%20CQ%2FAA%20instance.%20This%20is%20something%20we%20want%20to%20change%20in%20the%20future.%20the%20error%20you%20mentioned%20is%20a%20know%20issue%20on%20the%20portal%2C%20they%20are%20looking%20at%20it.%20if%20you%20try%20using%20Cmdlets%20it%20should%20work%20fine.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-665537%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-665537%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F86946%22%20target%3D%22_blank%22%3E%40Paul%20Coward%3C%2FA%3E%26nbsp%3Bincoming%20CQ%20call%20to%20an%20agent%20on%20VVX%20will%20display%20the%20Caller%20ID%20and%20the%20SIP%20URI%20name%20of%20the%20queue.%20Polycom%20have%20completed%20the%20fix%20to%20change%20the%20SIP%20URI%20to%20the%20given%20CQ%20name%20instead%2C%20the%20new%20firmware%20will%20start%20rolling%20out%20soon.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-665541%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-665541%22%20slang%3D%22en-US%22%3E%3CP%3EHas%20anyone%20successfully%20created%20a%20new%20CQ%20by%20creating%20a%20new%20resource%20account%20and%20assigning%20a%20hybrid%20number%20and%20the%20resource%20account%20to%20a%20CQ%20and%20have%20it%20actually%20work%3F%3C%2FP%3E%3CP%3EIf%20so%20can%20you%20share%20your%20process%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-665545%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-665545%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F351990%22%20target%3D%22_blank%22%3E%40cnx-michaelrlawrence%3C%2FA%3E%26nbsp%3B%20this%20is%20phone%20number%20porting%20issue%2C%20not%20related%20to%20auto%20attendants.%20send%20me%20the%20ticket%20number%20please%20and%20I%20will%20forwarded%20it%20to%20the%20appropriate%20team%20to%20advice%20on%20the%20way%20forward.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-665549%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-665549%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F54252%22%20target%3D%22_blank%22%3E%40Craig%20Aston%3C%2FA%3E%26nbsp%3B%20this%20issue%20is%20already%20highly%20prioritized.%20The%20work%20to%20remove%20the%20Calling%20Plan%20requirement%20for%20a%20service%20number%20is%20already%20undergoing%20and%20will%20be%20rolled-out%20soon%2C%20hopefully%20in%20a%20week.%20the%20%240%20Virtual%20User%20license%20to%20replace%20Phone%20System%20license%20is%20completed%20and%20in%20testing%20and%20validation%2C%20and%20the%20SKU%20is%20already%20being%20published%20for%207%2F1.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-665550%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-665550%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F294336%22%20target%3D%22_blank%22%3E%40KeepingITreal%3C%2FA%3E%26nbsp%3Bdid%20you%20happen%20to%20file%20the%20GUI%20bug%20regarding%20the%20PSTN%20number%20assignment%20change%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-665774%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-665774%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F85%22%20target%3D%22_blank%22%3E%40Jamie%20Stark%3C%2FA%3EHave%20you%20had%20a%20chance%20to%20look%20into%20the%20hotkey%20issues%3F%20It's%20getting%20very%20frustrating%20navigating%20and%20using%20the%20Teams%20admin%20portal.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams-Blog%2FAuto-Attendant-and-Call-Queues-Service-Update%2Fbc-p%2F633309%2Fhighlight%2Ftrue%23M3070%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams-Blog%2FAuto-Attendant-and-Call-Queues-Service-Update%2Fbc-p%2F633309%2Fhighlight%2Ftrue%23M3070%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-665953%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-665953%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20ported%20our%20office%20numbers%20last%20Thursday%20morning%20at%209a%2C%20in%20an%20effort%20to%20move%20to%20a%20Teams%20Only%20configuration.%20%26nbsp%3BToday%20was%20the%20third%20day%20our%2034%20year%20old%20architectural%20firm%20has%20been%20without%20%26nbsp%3Btelephones.%20We%20can%20not%20call%20out%20or%20receive%20a%20call.%20I%20have%20tried%20to%20work%20with%20support%20through%205%20separate%20service%20tickets%20and%20still%20no%20success.%20I%20left%20the%20office%20today%20with%20the%20technician%20telling%20me%20he%20would%20review%20our%20logs%20and%20contact%20the%20porting%20team.%20Tomorrow%20is%20day%20four.%20What%20a%20complete%20mess!%20I%20have%20now%20a%20CQ%20and%20AA%20with%20an%20E3%2C%20calling%20plan%20and%20domestic%20calling%20plan%20license.%20Calls%20into%20the%20office%20are%20answered%20by%20AA%20but%20users%20are%20prevented%20from%20answering%20the%20call%20and%20can%20not%20make%20an%20outbound%20call.%20How%20do%20I%20get%20this%20resolved%3F%20Who%20at%20Microsoft%20can%20help%3F%20Any%20ideas%20would%20be%20greatly%20appreciated.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-666103%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-666103%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F353999%22%20target%3D%22_blank%22%3E%40TreyWood%3C%2FA%3E%26nbsp%3BI%20would%20start%20making%20preperations%20for%20the%20worst%20if%20you%20havent%20already.%20The%20support%20team%20will%20not%20be%20able%20to%20help%20you%2C%20their%20hands%20are%20tied.%20This%20%22FeAtuRe%20UpDate%22%20is%20a%20DevOps%20dumpster%20fire%20which%20has%20compromised%20the%20basic%20functionality%20of%20the%20service.%20It's%20clear%20Microsoft%20is%20more%20intrested%20in%20ramming%20untested%20%22FeAtuRe%20UpDates%22%20down%20our%20throats%20then%20delivering%20a%20stable%2C%20working%20product.%20I'm%20sorry%20for%20the%20grim%20news%2C%20hopefully%20my%20post%20will%20save%20you%20sometime%20and%20frustration%20dealing%20with%20support.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-666424%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-666424%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%26nbsp%3B%3A%20Thanks%20for%20the%20info.%20Can%20you%20please%20let%20me%20know%20the%20cmdlet%20to%20do%20the%20redirection.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-666545%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-666545%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F86946%22%20target%3D%22_blank%22%3E%40Paul%20Coward%3C%2FA%3E%26nbsp%3BPolycom%20Firmware%205.9.2%20resolves%20this%20problem%20for%20us.%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20651px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F117089i56932295ABDFC843%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Polycom.png%22%20title%3D%22Polycom.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.polycom.com%2Fcontent%2Fdam%2Fpolycom-support%2Fproducts%2Fvoice%2Fbusiness-media-phones%2Frelease-notes%2Fen%2Fuc-software-release-notes-5-9-2.pdf%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.polycom.com%2Fcontent%2Fdam%2Fpolycom-support%2Fproducts%2Fvoice%2Fbusiness-media-phones%2Frelease-notes%2Fen%2Fuc-software-release-notes-5-9-2.pdf%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-666548%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-666548%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F353999%22%20target%3D%22_blank%22%3E%40TreyWood%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20have%20considered%20(but%20not%20yet%20actually%20tried%20in%20Teams%20-%20SfB%20was%20OK%20although%20the%20delegates%20sometimes%20were%20not%20able%20to%20be%20selected%20and%20note%20it%20didn't%20work%20if%20your%20users%20were%20across%20different%20SIP%20domains)%20assigning%20the%20main%20line%20number%20to%20a%20user%20which%20the%20porting%20team%20can%20arrange%20(I%20believe%20service%20numbers%20ported%20in%20can%20be%20assigned%20to%20both%20types)%20then%20distribute%26nbsp%3Bcalls%20via%20delegates%20(or%20boss%2Fadmin%20sometimes%20referred%20to).%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ESome%20other%20benefits%20maybe...%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EYou%20can%20also%20make%20calls%20on%20behalf%20of%20said%20user%20too%20(skype%20right%20click%20contact%20-%20call%2C%20on%20behalf%20of%20%2F%26nbsp%3B%20polycom%20VVX%20press%20and%20hold%20button)%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EMainline%20'user'%20could%20have%20a%20shared%20mailbox%20for%20vm's.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ESeems%20we%20have%20to%20pay%20for%20the%20license%20in%20any%20case.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20hope%20this%20is%20where%20MS%20is%20taking%20it%20-%20mainline%20number%20-%26gt%3B%20call%20queue%20with%20shared%20mailbox%20for%20VM%20etc.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-666596%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-666596%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F353999%22%20target%3D%22_blank%22%3E%40TreyWood%3C%2FA%3E%26nbsp%3BI've%20contacted%20the%20porting%20team%20directly%20at%26nbsp%3Bptn%40microsoft.com.%20They%20are%20really%20helpful%20and%20fast.%20They%20can%20also%20change%20user%20numbers%20to%20service%20numbers%20and%20back.%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Ftransferring-phone-numbers-common-questions%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Ftransferring-phone-numbers-common-questions%3C%2FA%3E%3C%2FP%3E%3CP%3EUsers%20will%20need%20a%20calling%20plan%20to%20assign%20a%20number.%20You%20can%20then%20add%20them%20in%20a%20group%20which%20are%20agents%20in%20the%20call%20queue.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-667039%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-667039%22%20slang%3D%22en-US%22%3E%3CP%3EEver%20since%20this%20moved%20to%20teams%20we%20are%20unable%20to%20create%20new%20AA%20or%20CQ%2C%20I%20have%20a%20ticket%20open%20with%20MS%20but%20they%20are%20not%20getting%20anywhere%20with%20a%20fix%2C%20this%20has%20now%20been%203%20weeks%20without%20this%20feature%20and%20is%20very%20poor%20from%20MS%2C%20im%20sure%20if%20I%20rolled%20out%20a%20service%20to%20my%20customer%20without%20testing%20it%20I%20would%20be%20in%20big%20trouble%20!!!%20MS%20just%20seem%20to%20do%20whatever%20they%20like....%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-667640%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-667640%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3EIt's%20actually%20not%20a%20porting%20issue.%26nbsp%3B%20It's%20the%20same%20issue%20others%20are%20having%20with%20the%20auto%20attendant%20and%20call%20queues.%26nbsp%3B%20I%20have%20a%20newly%20created%20resource%20account%20that%20is%20licensed%20properly%20of%20which%20I%20cannot%20assign%20a%20service%20number%2C%20nor%20have%20I%20been%20able%20to%20for%20a%20week.%26nbsp%3B%20I%20have%20service%20numbers%20we%20pulled%20from%20Microsoft%20and%20our%20main%20%22published%22%20telephone%20number%20we%20ported%20from%20Vonage%20that%20was%20ported%20in%20as%20a%20user%20number%20and%20then%20converted%20to%20a%20service%20number%20by%20the%20porting%20team%20so%20we%20could%20assign%20it%20to%20the%20resource%20account%20for%20our%20auto%20attendant%3B%20all%20of%20which%20still%20cannot%20be%20assigned%20to%20our%20resource%20account.%26nbsp%3B%20So%20not%20a%20porting%20issue.%26nbsp%3B%20Just%20the%20same%20issue%20many%20have%20expressed%20problems%20with%20in%20this%20thread.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20a%20temporary%20fix%2C%20we%20contacted%20the%20porting%20team%20to%20convert%20our%20main%20%22published%22%20telephone%20number%20back%20to%20a%20user%20number%20so%20we%20could%20at%20least%20get%20inbound%20calls.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENonetheless%2C%20the%20ticket%20number%20is%26nbsp%3B14563667.%26nbsp%3B%20Please%20do%20what%20you%20can%20to%20get%20this%20matter%20resolved.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-670394%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-670394%22%20slang%3D%22en-US%22%3E%3CDIV%20class%3D%22lia-message-body-wrapper%20lia-component-message-view-widget-body%22%3E%3CDIV%20class%3D%22lia-message-body%22%3E%3CDIV%20class%3D%22lia-message-body-content%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%26nbsp%3B%20would%20you%20please%20let%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F85%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3E%40Jamie%20Stark%3C%2FA%3E%20know%20that%20I%20have%20answered%20his%20questions%20in%20regards%20to%20the%20UI%20issues%20in%20the%20Teams%20admin%20portal%20two%20weeks%20ago%20already%3F%20It's%20getting%20%3CSTRONG%3Every%20frustrating%3C%2FSTRONG%3E%20navigating%20and%20using%20the%20Teams%20admin%20portal.%20The%20answer%20will%20be%20found%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams-Blog%2FAuto-Attendant-and-Call-Queues-Service-Update%2Fbc-p%2F633309%2Fhighlight%2Ftrue%23M3070%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams-Blog%2FAuto-Attendant-and-Call-Queues-Service-U...%3C%2FA%3E%3C%2FP%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-673628%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-673628%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20the%20worst%20Update%20on%20365%20I%20experienced%20myself%20so%20far.%20So%20many%20things%20broke%20and%20you%20cannot%20setup%20or%20change%20stuff%20properly.%20Ticket%20with%20Support%20is%20now%20open%20for%203%20weeks%20and%20attempts%20to%20solve%20our%20issues%20have%20made%20it%20even%20worse%20e.g.%20breaking%20additional%20existing%20number%20assignments.%20On%20top%20of%20all%20the%20issues%20mentioned%2C%20licensing%20requirements%20are%20a%20joke.%20Not%20even%20talking%20about%20how%20not%20having%20telephony%20working%20properly%20is%20affecting%20businesses'%20revenue%20and%20reputation%20or%20other%20activities%20like%20recruiting%20in%20our%20case.%20What.%20The.%20Hell.%203%20weeks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-673858%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-673858%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F93194%22%20target%3D%22_blank%22%3E%40Edmundo%20Pena%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F86946%22%20target%3D%22_blank%22%3E%40Paul%20Coward%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F88200%22%20target%3D%22_blank%22%3E%40Jef%20Vleugels%3C%2FA%3E%26nbsp%3B%20Update%3A%20I%20posted%20Monday%20concerning%20our%20firm's%20porting%20of%20numbers%20to%20MS%20toward%20a%20Teams%20Only%20configuration%20for%20our%20telephony.%20I%20thought%20I%20would%20provide%20an%20update.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EToday%20is%201%20week%20after%20porting%20and%20our%20firm%20STILL%20HAS%20NO%20OPERATIONAL%20phone%20system.%20I%20have%20been%20told%20day%20after%20day%20to%20be%20patient%2C%20%22the%20backend%20team%20is%20working%20on%20your%20problem%22...%20We%20have%20a%20working%20AA%20and%20CQ.%20The%20AA%20transfers%20an%20incoming%20call%20to%20the%20CQ%20attendant%20group%20which%20rings%20every%20client%20with%20an%20%22available%22%20presence.%20When%20the%20call%20is%20attempted%20to%20be%20answered%2C%20a%20window%20pops%20up%20with%20a%20%22Sorry%2C%20we%20couldn't%20connect%20you.%22%20message.%20The%20same%20message%20(different%20graphic%20format)%20appears%20when%20a%20client%20attempts%20to%20call%20out.%20All%20clients%20have%20E3%2C%20Phone%20System%20and%20Domestic%20calling%20plan%20licenses.%20The%20AA%20service%20number%20was%20ported%20to%20MS%20and%20has%20been%20our%20number%20since%201985.%20The%20CQ%20service%20number%20was%20provided%20new%20by%20MS%20during%20the%20configuration.%20The%20support%20engineer%20assures%20me%20that%20the%20AA%20and%20CQ%20are%20%22working%22%2C%20but%20the%20bottom%20line%20is%20that%20our%20phone%20system%20has%20been%20down%20a%20week.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEdmundo%2C%20your%20advice%20to%20plan%20for%20worst%20case%20is%20daily%20becoming%20apparent%20as%20good%20advice.%20However%3B%20frankly%20I%20want%20the%20Teams%20only%20configuration%20and%20at%20this%20point%20I%20have%20two%20options...Wait%20or%20start%20a%20porting%20plan%20away%20from%20MS%20to%20my%20previous%20carrier%20which%20took%20a%20month%20to%20happen%20the%20first%20time...VERY%20FRUSTRATING...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-673884%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-673884%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F353999%22%20target%3D%22_blank%22%3E%40TreyWood%3C%2FA%3E%26nbsp%3Byou%20can%20request%20an%20expidited%20port%20from%20the%20winning%20carrier%20PST%40Microsoft.com%20is%20good%20about%20facilitating%20these%20requests.%20If%20I%20was%20in%20your%20position%20I%20would%20pull%20that%20trigger%20right%20away.%20I've%20been%20doing%20this%20long%20enough%20to%20know%20the%20solution%20isn't%20going%20to%20be%20a%20fast%20one.%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%26nbsp%3Bis%20saying%207%2F1%20for%20%22free%20for%20now%22%20auto%20attendant%2Fcall%20queue%20licenses.%20Microsoft%20has%20resorted%20to%20testing%20in%20production%2C%20you%2C%20I%20and%20the%20rest%20of%20the%20Cloud%20Telephony%20consumerbase%20are%20besides%20ourselves%20with%20this%20latest%20change.%20You%20are%20being%20lead%20on%20just%20like%20the%20rest%20of%20us%2C%20the%20support%20team%20and%20devops%20teams%20are%20not%20communicating.%20They%20are%20telling%20you%20what%20you%20need%20to%20hear%20to%20stop%20calling%20because%20they%20can't%20do%20anything%20for%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-674644%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-674644%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F353999%22%20target%3D%22_blank%22%3E%40TreyWood%3C%2FA%3E%26nbsp%3BI%20myself%20hate%20when%20people%20are%20asking%20obvious%20questions%20%3A)%3C%2Fimg%3E%20but%20I%20will%20ask%20some%20obvious%20questions%3A%3C%2FP%3E%3CUL%3E%3CLI%3Eall%20clients%20have%20licenses%2C%20but%20also%20have%20a%20number%20assigned%20through%20powershell%3F%20In%20my%20experience%20this%20is%20for%20now%20the%20only%20sure%20way%20of%20assigning%20numbers%20(user%20numbers%20and%20service%20numbers)%26nbsp%3B%3CSPAN%3EGet-CsOnlineVoiceUser%20and%20Set-CsOnlineVoiceUser%2C%20Set-CsOnlineVoiceApplicationInstance...%20Or%20the%20legacy%20Skype%20for%20business%20portal%20works%20also%20for%20assigning%20user%20numbers.%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EWhich%20endpoints%20are%20the%20persons%20using%3F%20Teams%20client%20with%20headset%3F%26nbsp%3B%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EAre%20incoming%20calls%20to%20a%20user%20directly%20working%3F%20Not%20through%20AA%20or%20CQ.%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-674943%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-674943%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F353999%22%20target%3D%22_blank%22%3E%40TreyWood%3C%2FA%3E%26nbsp%3Bcontact%20me%20please%20in%20a%20private%20message%20with%20the%20ticket%20number%20and%20your%20contact%20information%2C%20I%20will%20check%20on%20the%20status%20and%20get%20back%20to%20you.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-674960%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-674960%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F78207%22%20target%3D%22_blank%22%3E%40Avijit%20Chakraborty%3C%2FA%3E%26nbsp%3B%20you%20can%20use%20the%20Teams%20admin%20portal%20to%20transfer%20an%20AA%20call%20to%20CQ%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FMicrosoftTeams%2Fcreate-a-phone-system-auto-attendant%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FMicrosoftTeams%2Fcreate-a-phone-system-auto-attendant%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-674977%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-674977%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F70184%22%20target%3D%22_blank%22%3E%40Kevin%20Sanders%3C%2FA%3E%26nbsp%3Bcan%20you%20shed%20some%20light%20on%20the%20issue%20please%3F%20what%20is%20breaking%20the%20creation%20of%20AA%2FCQ%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-674978%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-674978%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20an%20opinion%2C%20but%20if%20I%20ran%20my%20company%20I%20would%20not%20be%20using%20MS%20as%20a%20PBX%20provider%2C%20Avaya%2C%20Cisco%20etc%20have%20been%20doing%20this%20for%20years%2C%20and%20L3%20BT%20Verizon%20etc%20have%20been%20providing%20numbers%20and%20PSTN%20circuits%20for%20years%20without%20any%20major%20issues%2C%20now%20why%20would%20you%20want%20your%20phone%20service%20to%20be%20provided%20by%20MS%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-675007%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-675007%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%26nbsp%3Byes%20we%20are%20unable%20to%20create%20any%20at%20all%2C%20either%20by%20web%20or%20PS%2C%20also%20we%20can%20no%20longer%20manage%20the%20existing%20ones%20either%2C%20It%20seems%20to%20be%20the%20creation%20of%20the%20resource%20account%20that%20is%20the%20problem%2C%20its%20been%204%20weeks%20and%20still%20not%20working%2C%20this%20is%20really%20poor%20fro%20MS%20to%20push%20a%20service%20to%20a%20new%20platform%20and%20it%20fails%20is%20shocking%20really%2C%20if%20I%20did%20that%20I%20would%20have%20a%20recovery%20plan%20but%20its%20seems%20MS%20don't%20bother%20with%20that.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-675022%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-675022%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F70184%22%20target%3D%22_blank%22%3E%40Kevin%20Sanders%3C%2FA%3E%26nbsp%3B%20send%20me%20the%20ticket%20number%20and%20your%20tenant%20number%20in%20a%20private%20message%20please%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-675136%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-675136%22%20slang%3D%22en-US%22%3E%3CP%3EPosting%20here%20for%20the%20benefit%20of%20all%2C%20as%20I've%20been%20working%20with%20multiple%20threads%20in%20private%20messages.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%20have%20a%20broken%20AA%2FCQ%20service%20experience%20related%20to%20(AA%2FCQ%20not%20working%2C%20service%20numbers%20connected%20to%20AA%2FCQ%20not%20working%2C%20broken%20resource%20accounts...)%20please%20send%20me%20the%20following%20information%20in%20a%20private%20message%2C%20I%20have%20a%20dedicated%20developer%20to%20look%20into%20these%20cases%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E-%20Tenant%20ID%20and%20resource%20account%20ID%3A%20using%20this%20Cmdlet%20Get-csonlineapplicationendpoints%3C%2FP%3E%0A%3CP%3E-%20Support%20ticket%20number%3C%2FP%3E%0A%3CP%3E-%20your%20contact%20information%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-677285%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-677285%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F80266%22%20target%3D%22_blank%22%3E%40Ryan%20Steele%3C%2FA%3Egood%20work!%20%3AD%3C%2Fimg%3E%20Ill%20give%20this%20a%20try.%20If%20it%20works%20for%20me%20too%20I%20might%20point%20Microsoft%20Support%20in%20this%20direction%20too%20haha!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-677874%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-677874%22%20slang%3D%22en-US%22%3E%3CP%3EFollowing%20to%20see%20when%20in%20%22summer%22%20this%20GA's%3A%26nbsp%3B%20%22%3CSTRONG%3ETransfer%20to%20PSTN%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3Band%20extension%20dialing%20is%20work%20in%20progress%2C%20we%20expect%20to%20make%20them%20available%20by%20summer.%22%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-678020%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-678020%22%20slang%3D%22en-US%22%3E%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20Calibri%3B%20font-size%3A%2011.0pt%3B%22%3EUpdate%3A%20Calling%20Plan%20requirement%20for%20assigning%20a%20service%20number%20to%20a%20resource%20is%20removed%2C%20roll-out%20is%20expected%20to%20be%20completed%20this%20week%20and%20documentation%20will%20be%20updated%20accordingly.%20Virtual%20User%20%240%20license%20to%20replace%20the%20Phone%20System%20requirement%20is%20still%20on-track%20for%20July%201st.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-678042%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-678042%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%26nbsp%3B%20A%20response%20to%20this%20issue%20please%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams-Blog%2FAuto-Attendant-and-Call-Queues-Service-Update%2Fbc-p%2F633309%2Fhighlight%2Ftrue%23M3070%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams-Blog%2FAuto-Attendant-and-Call-Queues-Service-Update%2Fbc-p%2F633309%2Fhighlight%2Ftrue%23M3070%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-678948%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-678948%22%20slang%3D%22en-US%22%3E%3CP%3EUpdate%20to%20this%20community%3A%2010%20days%20ago%2C%20I%20ported%20my%20firm's%20PSTN%20numbers%20to%20Microsoft.%20It%20took%20a%20day%20or%20so%20to%20get%20the%20AA%20and%20CQ%20operational%3B%20but%20my%20clients%20were%20unable%20to%20answer%20the%20incoming%20calls%20or%20make%20outgoing%20calls.%20I%20had%205%20service%20tickets%20open%20attempting%20to%20resolve%20this.%20These%205%20tickets%20were%20combined%20into%20one%20ticket%20for%204%20days%20and%20until%20this%20morning%20our%20telephone%20system%20was%20not%20working.%20Thankfully%2C%20now%20it%20is%20operational.%20This%20message%20is%20intended%20to%20explain%20how%20this%20resolution%20came%20to%20be.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%208%20or%20so%20days%2C%20I%20was%20told%20by%20the%20support%20engineer%20%22the%20backend%20Team%20is%20working%20on%20your%20issue...please%20be%20patient...%22.%20I%20shared%20with%20this%20blog%20my%20situation%20on%20Monday%20and%20then%20provided%20an%20update%20Thursday%20morning.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELater%20Thursday%2C%20the%20moderator%20of%20this%20page%2C%20Waseem%20(CHAMPION)%20Hashem%2C%20contacted%20me%20and%20asked%20that%20I%20send%20to%20him%20some%20information.%20He%20called%20me%20the%20next%20day%20around%202p%20and%20listened%20and%20probed%20for%20more%20information.%20He%20followed%20up%20by%20email%203%20hours%20later%20with%20an%20update.%20He%20then%20followed%20up%203%20hours%20later%20with%20a%20solution%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMessage%20from%20Waseem%3A%3C%2FP%3E%3CP%3E%22seems%20like%20you%20have%20Location%20Based%20Routing%20is%20enabled%20for%20users%2C%20and%20that's%20what's%20failing%20the%20calls.%20This%20feature%20is%20to%20prevent%20toll-bypass%20for%20some%20countries%20that%20have%20regulations%20for%20that%2C%20such%20as%20India.%20if%20this%20was%20not%20configured%20intentionally%2C%20please%20remove%20it%20by%20setting%26nbsp%3BPreventTollBypass%20to%20false%20in%20this%20policy%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fskype%2Fset-csteamscallingpolicy%3Fview%3Dskype-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fskype%2Fset-csteamscallingpolicy%3Fview%3Dskype-ps%22%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20made%20the%20change%20here%3A%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20809px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F117524i2911555819428610%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Teams%20config.JPG%22%20title%3D%22Teams%20config.JPG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3ETHANK%20YOU%20Waseem!%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-679006%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-679006%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%26nbsp%3Bwhen%20will%20the%20creation%20of%20AA's%20and%20Call%20Queues%20be%20quicker%3F%26nbsp%3B%20Once%20I%20build%20them%20in%20the%20Teams%20Admin%20Center%20I%20can't%20do%20anything%20with%20them%20for%2024%20hours%2C%20If%20I%20try%20to%20link%20an%20AA%20to%20a%20CQ%20or%20vice%20versa%20after%20building%20them%20I%20get%20an%20error%20or%20notice%20that%20it%20can't%20update%20the%20call%20handler.%26nbsp%3B%20In%20the%20old%20SfB%20Admin%20Portal%20we%20were%20able%20to%20build%20and%20use%20these%20in%20minutes%20and%20now%20it%20takes%20days%2C%20this%20needs%20to%20be%20fixed%20asap.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-679102%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-679102%22%20slang%3D%22en-US%22%3E%3CP%3EAgree%20with%20above%2C%20replication%20times%20in%20O365%20are%20way%20too%20long.%20It%20makes%20troubleshooting%20and%20migrations%20difficult.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-680628%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-680628%22%20slang%3D%22en-US%22%3E%3CP%3E3.%20You%20can%20assign%20a%20%3CSTRONG%3Ehybrid%20number%3C%2FSTRONG%3E%20to%20AA%2FCQ%20(in%20public%20preview)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20this%20still%20public%20preview%3F%20When%20will%20this%20be%20GA%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-682189%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-682189%22%20slang%3D%22en-US%22%3E%3CP%3EQuick%20update%2C%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%20everyone%20for%20contacting%20me%20to%20follow-up%20on%20your%20cases%2C%20I%20still%20have%20couple%20of%20calls%20and%20follow-ups%20to%20close%20on%20with%20some%20of%20you.%20However%2C%20almost%20all%20the%20cases%20that%20were%20related%20to%20AA%2FCQ%20are%20due%20to%20a%20known%20issue%2C%20which%20is%20the%20%3CSTRONG%3EResource%20Account%20sync%20delay%3C%2FSTRONG%3E!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20delay%20causes%20a%20lot%20of%20you%20to%20naturally%20try%20different%20things%20that%20is%20unfortunately%20making%20it%20worst%2C%20and%20in%20some%20cases%20getting%20the%20resource%20account%20corrupted.%20We're%20working%20on%20this%20issue%2C%20but%20until%20we%20fix%20it%20make%20sure%20to%3A%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3ECreate%20the%20resource%20account%20%26nbsp%3B%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3EAssign%20license%3C%2FLI%3E%0A%3CLI%3EAllow%2024h%20for%20it%20to%20sync%3C%2FLI%3E%0A%3CLI%3EThen%20assign%20the%20phone%20number%3C%2FLI%3E%0A%3CLI%3EDo%20not%20delete%20it%20before%20its%20synced%3C%2FLI%3E%0A%3CLI%3EIf%20you%20did%20already%2C%20create%20a%20new%20one%20with%20a%20%3CSTRONG%3Edifferent%20name.%20%3C%2FSTRONG%3ECreating%20a%20new%20one%20with%20the%20same%20name%20is%20not%20going%20to%20work.%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3EDo%20not%20change%20the%20license%20once%20assigned%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3EHere%E2%80%99s%20a%20list%20of%20the%20known%20issues%20we%E2%80%99re%20working%20through%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CTABLE%20width%3D%22888%22%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22360%22%3E%3CP%3ESymptom%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22246%22%3E%3CP%3EMitigation%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22282%22%3E%3CP%3EIssue%20Description%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22360%22%3E%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20AA%2FCQ%20is%20not%20functional%3C%2FP%3E%0A%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Not%20able%20to%20assign%20a%20phone%20number%3C%2FP%3E%0A%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20You%E2%80%99re%20getting%20a%20message%20%E2%80%9Cthe%20following%20application%20instance%20is%20not%20present%20in%20BVD%E2%80%9D%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22246%22%3E%3CP%3EAllow%2024h%20sync.%20If%20it%20has%20been%20already%2024h%2C%20make%20sure%20you%20remove%20the%20phone%20number%20assignment%20then%20delete%20the%20RA%2C%20and%20create%20a%20new%20one%20with%20a%20different%20name.%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22282%22%3E%3CP%3EBVD%20Sync%20Delay%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22360%22%3E%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Cannot%20change%20phone%20number%3C%2FP%3E%0A%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20You%E2%80%99re%20getting%20an%20error%20%E2%80%9CCannot%20sync%20to%20BVD%E2%80%9D%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22246%22%3E%3CP%3EUse%20Cmdlet%20instead%20of%20the%20portal%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22282%22%3E%3CP%3EDepartment%20parameter%20is%20not%20set%20properly%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22360%22%3E%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Cannot%20assign%20a%20toll-number%20(service%20number)%20from%20admin%20portal%3C%2FP%3E%0A%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Admin%20portal%20returning%20error%20%E2%80%9Cyou%20need%20a%20phone%20system%20license%E2%80%9D%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22246%22%3E%3CP%3EUse%20Cmdlet%20to%20do%20that%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22282%22%3E%3CP%3EAdmin%20Portal%20have%20an%20issue%20with%20toll-number%20assignment%2C%20and%20its%20returning%20the%20wrong%20error%20message%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22360%22%3E%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Admin%20portal%20returning%20error%20%E2%80%9CCall%20Handler%E2%80%A6%E2%80%9D%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22246%22%3E%3CP%3EResource%20account%20is%20not%20synced%2C%20or%20corrupted.%20Wait%20for%20it%20to%20sync%20or%20create%20a%20new%20one.%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22282%22%3E%3CP%3EWrong%20error%20message%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22360%22%3E%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Resource%20account%20not%20working%3C%2FP%3E%0A%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20SIP%20URI%20disappears%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22246%22%3E%3CP%3ECreate%20a%20new%20RA%20with%20a%20different%20SIP%20URI%20name%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22282%22%3E%3CP%3ERemoving%20phone%20system%20license%20corrupts%20the%20resource%20account.%20Creating%20a%20new%20one%20with%20the%20same%20SIP%20URI%20will%20not%20work%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22360%22%3E%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Phone%20number%20blocked%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22246%22%3E%3CP%3EContact%20MS%20to%20release%20the%20TN%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22282%22%3E%3CP%3EDeleting%20the%20resource%20account%20before%20removing%20the%20TN%20will%20block%20the%20phone%20number.%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-682190%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-682190%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F77618%22%20target%3D%22_blank%22%3E%40Mark%20Linman%3C%2FA%3E%26nbsp%3B%20the%20previous%20service%20did%20not%20have%20a%20dependency%20on%20the%20resource%20account%20and%20that's%20why%20it%20did%20not%20impact%20it.%20The%20sync%20delay%20fix%20is%20unfortunately%20not%20trivial%2C%20we%20started%20working%20on%20it%20but%20will%20take%20some%20time.%20will%20update%20the%20community%20with%20the%20timeline%20once%20we%20have%20confidence%20in%20the%20fix.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-682191%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-682191%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F343441%22%20target%3D%22_blank%22%3E%40jguel%3C%2FA%3E%26nbsp%3BETA%20is%20next%20week.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-683193%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-683193%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20you%20could%20shed%20some%20light%20on%20this....%3C%2FP%3E%3CP%3EHere%20is%20the%20issue%20i'm%20running%20into%20with%20a%20customer.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20trying%20to%20'move'%20their%20on%20premises%20Skype%20Server%20IVR%2FHunt%20Group%20to%20Cloud%20Phone%20System%20Auto%20Attendant.%3C%2FP%3E%3CP%3EFollowed%20all%20the%20steps%20in%20this%20article%20to%20create%20the%20on%20premises%20HybridApplicationEndpoint....%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fskypeforbusiness%2Fhybrid%2Fconfigure-cloud-auto-attendant%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fskypeforbusiness%2Fhybrid%2Fconfigure-cloud-auto-attendant%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAllowed%20the%20on%20premises%20account%20to%20sync%20to%20Office%20365%2C%20licensed%20the%20blocked%20account%20with%20E5%2Fphone%20system.%3C%2FP%3E%3CP%3EAfter%2072%20hours%2C%20the%20AA%20still%20shows%20'Setting%20up'%20in%20the%20admin%20center.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20645px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F117772iAD2A2DCB0AB201E6%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%222019-06-10_17-02-38.jpg%22%20title%3D%222019-06-10_17-02-38.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eanyone%20run%20into%20this%20issue%2C%20does%20this%20even%20work%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-683335%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-683335%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%20We're%20having%20an%20issue%20with%20one%20of%20our%20migrated%20Auto%20Attendants.%20It's%20working%2C%20but%20looks%20like%20we%20can%20not%20open%20it%20and%20navigate%20between%20options%20(General%20Info%2C%20Business%20Hours%2C%20Business%20hours%20call%20settings%2C%20Holiday%20call%20settings%2C%20etc)%20I%20noticed%20when%20I%20first%20land%20on%20Voice%20-%26gt%3B%20Auto%20Attendants%2C%20I%20get%20an%3A%20Error%20We%20can't%20load%20all%20of%20your%20auto%20attendants.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-683343%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-683343%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%20We%20have%20ticket%20number%3A%2014401450%20opened%20that%20I%20have%20addressed%20this%20AA%20issue%20not%20opening%20-%20amongst%20other%20issues%20we've%20had.%20Thanks%20for%20looking%20into%20it.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-683348%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-683348%22%20slang%3D%22en-US%22%3EYeesh%2C%20sorry%2C%20ticket%20is%3A%2014442549%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-687700%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-687700%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3E%40Waseem%20Hashem%3C%2FA%3E%20Thanks%20for%20all%20the%20posts%20and%20info.%26nbsp%3B%20I%20am%20also%20having%20a%20very%20frustrating%20time%20completing%20the%20creation%20of%20these%20AAs%20and%20resource%20accounts.%26nbsp%3B%20I%20had%20the%20error%20'%3CSPAN%3Ethe%20following%20application%20instance%20is%20not%20present%20in%20BVD%3C%2FSPAN%3E'%20and%20followed%20your%20suggestion%20to%20create%20new%20RAs%20with%20different%20names%2Faddresses%2C%20waited%20the%2024%20hours%20after%20assigning%20the%20proper%20licenses%2C%20but%20I%20still%20cannot%20assign%20a%20service%20number%20to%20the%20RA.%26nbsp%3B%20Please%20help!%26nbsp%3B%20I%20have%20also%20been%20working%20with%20Premier%20Support%20(%3CFONT%3ETicket%20%23%3A14730674%3C%2FFONT%3E)%2C%20but%20have%20not%20gotten%20anywhere%20with%20this%20issue.%26nbsp%3B%20Only%20that%20the%20engineering%20team%20is%20working%20on%20getting%20this%20resolved.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20any%20help%20you%20can%20provide!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-690268%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-690268%22%20slang%3D%22en-US%22%3E%3CP%3EI%20was%20able%20to%20finally%20assign%20the%20resource%20account%20a%20phone%20number%20because%20the%20backend%20team%20made%20some%20change%20or%20had%20it%20complete%20provisioning%2C%20but%20now%20I%20cannot%20choose%20my%20Call%20Queue%2Fresource%20account%20for%20the%20Business%20hours%20call%20settings.%26nbsp%3B%20Error%3A%26nbsp%3B%20%22We%20can't%20create%20call%20handler%20at%20the%20moment.%22%20I%20don't%20think%20I%20had%20this%20many%20problems%20creating%20all%20this%20in%20the%20Skype%20Admin%20Center%20before.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-675952%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-675952%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3EEdit%3A%3C%2FSTRONG%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%26nbsp%3Bhas%20advised%20in%20a%20reply%20further%20down%20this%20thread%20that%20changing%20the%20license%20on%20a%20service%20account%20may%20cause%20corruption%2C%20so%20be%20warned.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegarding%20the%20current%20lack%20of%20a%20zero-cost%20license%20for%20new%20PSTN-enabled%20resource%20accounts%2C%20I've%20been%20performing%20a%20bit%20of%20a%20science%20experiment.%20On%20Tuesday%2C%20I%20created%20a%20new%20resource%20account%2C%20assigned%20Office%20365%20E3%2FPhone%20System%2FCalling%20Plan%20licenses%2C%20assigned%20a%20service%20number%2C%20and%20pointed%20it%20an%20an%20auto%20attendant.%20Then%20I%20removed%20all%20the%20licenses.%20Two%20days%20later%20and%20it's%20still%20working.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENo%20guarantees%20it%20won't%20stop%20working%20at%20any%20time%2C%20of%20course%2C%20but%20if%20anyone%20needs%20to%20create%20a%20bunch%20of%20PSTN-enabled%20resource%20accounts%2C%20doesn't%20want%20to%20purchase%20a%20bunch%20of%20licenses%20and%20is%20willing%20to%20take%20the%20risk...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-690547%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-690547%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%26nbsp%3B-%20Many%20thanks%20for%20the%20updates%20posted%20on%20this%20issue.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EIn%20reference%20to%20your%20post%20%22Update%3A%20Calling%20Plan%20requirement%20for%20assigning%20a%20service%20number%20to%20a%20resource%20is%20removed%2C%20roll-out%20is%20expected%20to%20be%20completed%20this%20week%20and%20documentation%20will%20be%20updated%20accordingly.%20Virtual%20User%20%240%20license%20to%20replace%20the%20Phone%20System%20requirement%20is%20still%20on-track%20for%20July%201st.%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EHas%20this%20roll-out%20been%20completed%2C%20since%20I%20cannot%20see%20the%20following%20has%20been%20updated%20since%2024th%20May%3A%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fcreate-a-phone-system-auto-attendant%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fcreate-a-phone-system-auto-attendant%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EPlease%20advise%20whether%20this%20still%20stands%20true%20in%20the%20creation%20of%20new%20AA%2FCQ%20involves%20the%20following%20steps%20if%20assigning%20a%20Microsoft%20Service%20number%3A%3C%2FSPAN%3E%3C%2FP%3E%3COL%3E%3CLI%3ECreate%20the%20resource%20account%20%26nbsp%3B%26nbsp%3B%3C%2FLI%3E%3CLI%3EAssign%20license%20(Calling%20Plan%20or%20no%20Calling%20Plan%20required%3F)%3C%2FLI%3E%3CLI%3EAllow%2024h%20for%20it%20to%20sync%3C%2FLI%3E%3CLI%3EThen%20assign%20the%20phone%20number%3C%2FLI%3E%3CLI%3EDo%20not%20delete%20it%20before%20its%20synced%3C%2FLI%3E%3CLI%3EDo%20not%20change%20the%20license%20once%20assigned%3C%2FLI%3E%3C%2FOL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-690597%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-690597%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3E%40Waseem%20Hashem%3C%2FA%3E%20I%20posted%20a%20new%20message%20about%202%20hours%20ago%2C%20since%20my%20initial%20post%20yesterday%2C%20and%20now%20having%20a%20different%20issue%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20was%20able%20to%20finally%20assign%20the%20resource%20account%20a%20phone%20number%20because%20the%20backend%20team%20made%20some%20change%20or%20had%20it%20complete%20provisioning%2C%20but%20now%20I%20cannot%20choose%20my%20Call%20Queue%2Fresource%20account%20for%20the%20Business%20hours%20call%20settings.%26nbsp%3B%20Error%3A%26nbsp%3B%20%22We%20can't%20create%20call%20handler%20at%20the%20moment.%22%20I%20don't%20think%20I%20had%20this%20many%20problems%20creating%20all%20this%20in%20the%20Skype%20Admin%20Center%20before.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-692025%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-692025%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F16254%22%20target%3D%22_blank%22%3E%40Waseem%20Hashem%3C%2FA%3E%20%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CFONT%20color%3D%22%23b00000%22%20face%3D%22Segoe%20UI%2CSegoeUI%2CSegoe%20WP%2CHelvetica%20Neue%2CHelvetica%2CTahoma%2CArial%2Csans-serif%22%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fcreate-a-phone-system-auto-attendant%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fcreate-a-phone-system-auto-attendant%3C%2FA%3E%3C%2FFONT%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EStates%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CEM%3E%3CSPAN%3EIf%20you%20are%20assigning%20a%20Microsoft%20service%20number%20instead%2C%20you%20need%20to%20acquire%20and%20assign%20the%20following%20licenses%20to%20your%20resource%20account%20(Office%20365%20Enterprise%20E1%2C%20E3%20or%20E5%2C%20with%20the%20Phone%20System%20add-on%20and%20a%20Calling%20Plan).%3C%2FSPAN%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EWhilst%20we%20are%20waiting%20on%20the%20free%20license%20(due%201%20July)%20Could%20you%20please%20confirm%20if%20we%20can%20use%20a%20%3CSTRONG%3ECommon%20Area%20Phone%3C%2FSTRONG%3E%20license%20bundle%20%2B%20Call%20Plan%2C%20rather%20than%20E1%20%2B%20Ph%20Sys%20%2B%20Calling%20plan%3F%20if%20not%20what%20is%20missing%20in%20that%20bundle%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMany%20Thanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-692106%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-692106%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F359014%22%20target%3D%22_blank%22%3E%40myry1%3C%2FA%3EI%20had%20the%20same%20issue%2C%20backend%20made%20some%20changes%20and%20now%20I%20am%20able%20to%20add%20a%20Call%20Queue%20however%20the%20call%20queue%20is%20not%20actually%20responding%20and%20the%20call%20cant%20be%20answered.%3C%2FP%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-692440%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-692440%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F118118i0F3602AAF1BBECE1%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22CommonAreaPhone%202019-06-14%20211059.jpg%22%20title%3D%22CommonAreaPhone%202019-06-14%20211059.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EWhat%20other%20license%20could%20an%20Auto-Attendant%20resource%20account%20require%20other%20than%20calling%20plan%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-693132%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-693132%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20some%20fairly%20large%20customers%20on%20SkypeOnline%20who%20has%20not%20yet%20started%20to%20move%20to%20Teams.%20(So%20no%20interop%20mode%20defined%2C%20planned%2C%20tested.)%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20way%20to%20-%20temporarily%20-%20opt%20out%20of%20this%20feature%20and%20stay%20on%20legacy%20SkypeOnline%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPs.%20MS%20created%20the%20impression%20earlier%20this%20year%20that%20deciding%20and%20declaring%20to%20stay%20on%20SkypeOnline%20means%20one%20gets%20the%20service%20(without%20changes%20of%20course)%20of%20SkypeOnline%20for%20a%20time%20being.%20Now%20it%20shows%20that%20even%20customers%20with%2010-20k%20of%20Phone%20licences%20can%20be%20forced%20to%20move%20to%20Teams%20in%20a%20not%20planned%20and%20scheduled%20way.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-693135%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-693135%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F360557%22%20target%3D%22_blank%22%3E%40G____%3C%2FA%3E%26nbsp%3BNot%20a%20chance.%20Microsoft%20is%20ramming%20Teams%20down%20our%20throat%20in%20the%20worst%20way%20possible.%20Alpha%2FBeta%20testing%20in%20production%2C%20this%20thread%20is%20a%20clear%20indication%20of%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-694613%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-694613%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20above%20frustration%20is%20coming%20from%20the%20below%20problem.%20Did%20anyone%20manage%20to%20work%20around%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3BNeed%20a%20new%20call%20Queue.%20OK%2C%20add%20a%20resource%20account%2C%20(request%20and)%20assign%20phone%20number%20and%20license.%20Doable%2C%20done.%20Then%20-%20as%20no%20Teams%20configured%20there%20is%20no%20UI%20option%20under%20Teams%20Voice%20section%20to%20create%20a%20Call%20Queue%20in%20Teams.%20So%20go%20to%20PowerShell%20and%20with%20the%20help%20of%20New-%20(or%20Set-)%20CsOnlineApplicationInstance%20you%20can%20add%20a%20new%20queue%20with%20groups%20and%20settings.%20Nice.%20Then%20you%20wanted%20to%20associate%20your%20queue%20with%20the%20previously%20created%20resource%20accounts.%3C%2FP%3E%3CP%3EHowever%2C%20the%20Resource%20account%20management%20UI%20(under%20Teams%20admin)%26nbsp%3B%20allows%20you%20to%20assign%20(associate)%20a%20queue%20to%20a%20resource%20account%20searching%20by%20PHONE%20NUMBER%20only.%20Even%20so%2C%20the%20phone%20number%20is%20on%20the%20resource%20account%20as%20a%20property.%26nbsp%3B%3C%2FP%3E%3CP%3EI%20was%20not%20able%20to%20find%20any%20PS%20command%20to%20connect%20them.%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20idea%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-694776%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-694776%22%20slang%3D%22en-US%22%3E%3CP%3EAgain%20something%20strange%20configuring%20AA%20and%20CQ%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3COL%3E%3CLI%3ECreated%20the%20resource%20accounts%3C%2FLI%3E%3CLI%3EAssigned%20licenses%3C%2FLI%3E%3CLI%3EAllowed%2024h%20for%20it%20to%20sync%3C%2FLI%3E%3CLI%3EThen%20assigned%20the%20phone%20numbers%3C%2FLI%3E%3CLI%3ECreated%20AA%20%26amp%3B%20CQ%3C%2FLI%3E%3CLI%3EAssigned%20O365%20Group%20to%20Created%3C%2FLI%3E%3CLI%3EAssigned%20Resource%20Accounts%20to%20AA%20and%20CQ%3C%2FLI%3E%3CLI%3EThere%20is%20still%20no%20way%20to%20redirect%20the%20AA%20Call%20to%20a%20Voice%20APP%20even%20using%20PS%20%3A%3C%2FLI%3E%3C%2FOL%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F118233iD9D5076E1524F753%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22error-AA-CQ-1.jpg%22%20title%3D%22error-AA-CQ-1.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEven%20using%20the%20Teams%20Admin%20Center%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20764px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F118232iB5FD7D76BF6305A3%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22error-AA-CQ.jpg%22%20title%3D%22error-AA-CQ.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EAnyone%20knows%20the%20problem%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMany%20thanks%20for%20your%20support%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-699336%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-699336%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20an%20issue%20regarding%20our%20direct%20route%20number%20attached%20to%20the%20new%20Teams%20call%20queue%20not%20connecting%20the%20inbound%20calls%20with%20the%20agent.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20call%20rings%20on%20the%20agent's%20teams%20client%20but%20when%20they%20click%20answer%20it%20reports%20Connecting..%20for%20about%2010%20seconds%20and%20then%20drops%20the%20call.%20Teams%20reports%20Leaving%20call%20or%20sometimes%20puts%20the%20call%20on%20hold%2C%20the%20external%20call%20always%20gets%20dropped%20after%20the%2010%20seconds%20even%20though%20the%20teams%20agent%20still%20seems%20to%20be%20connected%20either%20on%20hold%20or%20leaving%20call%2C%20then%20after%20a%20minute%20or%20so%20Teams%20reports%20sorry%20we%20couldn't%20connect%20you.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20anyone%20else%20seeing%20this%20with%20the%20new%20Teams%20call%20queues%2C%20as%20my%20support%20ticket%20doesn't%20seem%20to%20be%20going%20anywhere.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-700304%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-700304%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F167113%22%20target%3D%22_blank%22%3E%40Shane%20Toal%3C%2FA%3EI%20have%20a%20client%20that%20is%20running%20into%20a%20similar%20issue.%20We%20are%20using%20Auto%20Attendant%20with%20a%20call%20queue%20and%20when%20the%20client%20answers%20the%20phone%2C%20they%20are%20connected%20for%20half%20a%20second%20and%20then%20the%20call%20is%20placed%20on%20hold%20for%20about%2010%20seconds.%20The%20customer%20calling%20in%20hears%20nothing%20but%20silence%20and%20it%20sounds%20like%20the%20call%20was%20dropped%20resulting%20in%20hang-ups.%20My%20client%20is%20using%20Yealink%20phones%20and%20sees%20on%20the%20screen%20that%20the%20call%20is%20on%20hold%20and%20then%20a%20small%20message%20at%20the%20bottom%20that%20is%20saying%20%22An%20error%20occurred%20while%20answering%20a%20call%22.%20In%20our%20case%2C%20after%20the%2010%20seconds%2C%20the%20call%20was%20resumed%20but%20very%20few%20people%20were%20still%20on%20the%20line.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20don't%20have%20a%20solution%20for%20this%20yet%20but%20if%20you%20come%20across%20anything%20that%20works%20I%20would%20be%20very%20interested%20in%20knowing%20about%20it.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-700461%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-700461%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F362329%22%20target%3D%22_blank%22%3E%40ThaneBelnap%3C%2FA%3Ewe%20are%20having%20the%20same%20issue.%20Yealink%20devices.%20Also%20the%20call%20options%20are%20greyed%20out%2C%20for%20the%20transfer%20and%20hold%20function.%3CBR%20%2F%3EYou%20can%20use%20the%20hardkeys%20on%20the%20phone%20though.%20Nevertheless%2C%20the%20issue%20regarding%20a%20call%20being%20automatically%20on%20hold%20is%20the%20most%20urgent%20issue(!)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-700736%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-700736%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F275063%22%20target%3D%22_blank%22%3E%40PriyeshPindoria%3C%2FA%3E%26nbsp%3B%20requirement%20for%20Calling%20Plan%20was%20removed%20already%2C%20documentation%20are%20updated%20and%20will%20be%20published%20soon.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-700738%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-700738%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F359014%22%20target%3D%22_blank%22%3E%40myry1%3C%2FA%3E%26nbsp%3Bsend%20me%20the%20ticket%20number%20or%20your%20tenant%20ID%20please%20in%20a%20private%20message%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-700755%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-700755%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F294336%22%20target%3D%22_blank%22%3E%40KeepingITreal%3C%2FA%3E%26nbsp%3BCalling%20Plan%20requirement%20was%20removed%20already%2C%20no%20need%20to%20assign%20it%20for%20service%20numbers.%20Many%20customers%20reported%20that%20they%20used%20CAP%20licenses%20and%20it%20worked%20fine.%20Theoretically%20it%20should%20work%20fine%20since%20its%20a%20Phone%20System%20like%20license%2C%20however%20we%20do%20not%20promote%20the%20use%20of%20it%20since%20it%20was%20not%20tested%20and%20validated%20by%20our%20engineers.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-700775%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-700775%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F45624%22%20target%3D%22_blank%22%3E%40Pietro%20Rossini%3C%2FA%3E%26nbsp%3B%20is%20the%20resource%20account%20of%20the%20target%20application%20synced%20already%3F%20are%20you%20able%20to%20call%20it%20directly%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-700794%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-700794%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F11207%22%20target%3D%22_blank%22%3E%40Shane%20Toal%3C%2FA%3E%26nbsp%3B%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F362329%22%20target%3D%22_blank%22%3E%40ThaneBelnap%3C%2FA%3E%26nbsp%3B%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F40440%22%20target%3D%22_blank%22%3E%40Martijn%20Steffens%3C%2FA%3E%26nbsp%3B%20the%20Yealink%20placing%20call%20on%20hold%20is%20an%20Android%20App%20issue%20that%20was%20fixed%20per%20my%20understanding%2C%20will%20follow%20up%20with%20the%20team%20to%20find%20out%20where%20the%20fix%20is.%20On%20the%20direct%20routing%20call%20not%20connecting%2C%20there's%20a%20similar%20issue%20detected%20with%20DR%20configuration%20(SBC)%20and%20being%20investigated%20by%20the%20DR%20team.%20if%20you%20have%20a%20case%20opened%20with%20support%20they%20will%20update%20you%20once%20the%20resolution%20is%20shared.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-564521%22%20slang%3D%22en-US%22%3EAuto%20Attendant%20and%20Call%20Queues%20Service%20Update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-564521%22%20slang%3D%22en-US%22%3E%3CP%3EService%20update%20notification%3C%2FP%3E%3CP%3EThe%20service%20updates%20for%20Auto%20Attendant%20and%20Call%20Queues%20were%20completed%20successfully%20this%20week.%20The%20updates%20introduce%20new%20capabilities%2C%20namely%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%20Centralized%20holiday%20tables%20that%20can%20be%20reused%20across%20apps.%20You%20will%20find%20it%20under%20Org%20wide%20settings%3C%2FP%3E%3CP%3E2.%20You%20can%20assign%20Direct%20Routing%20numbers%20to%20Auto%20Attendant%20and%20Call%20Queues%20(as%20of%20today%20DR%20with%20AA%2FCQ%20support%20Teams%20users%20only)%3C%2FP%3E%3CP%3E3.%20You%20can%20assign%20a%20hybrid%20number%20to%20AA%2FCQ%20(OPCH%20Released%206%2F17%2C%20CCE%20is%20still%20in%20public%20preview)%3C%2FP%3E%3CP%3E4.%20You%20can%20assign%20Multiple%20numbers%20to%20an%20auto%20attendant%20or%20call%20queue%3C%2FP%3E%3CP%3E5.%20Round%20Robin%20routing%20option%20is%20introduced%20in%20call%20queues%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20updates%20prepare%20the%20services%20as%20well%20for%20the%20upcoming%20features%3A%3C%2FP%3E%3CP%3E6.%20Transfer%20out%20to%20PSTN%20from%20auto%20attendant%20and%20call%20queues%3C%2FP%3E%3CP%3E7.%20Extension%20dialing%20from%20auto%20attendant%3C%2FP%3E%3CP%3E8.%20Voicemail%20shared%20mailbox%20for%20auto%20attendant%20and%20call%20queues%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%E2%80%AF%3C%2FP%3E%3CP%3EWhat%20to%20expect%20after%20the%20service%20update%3F%3C%2FP%3EYou%20can%20now%20create%20auto%20attendants%20and%20call%20queues%20in%20Teams%20Admin%20Portal%20Your%20previous%20auto%20attendants%20and%20call%20queues%20were%20migrated%20to%20Teams%20Admin%20portal%2C%20and%20they%20should%20continue%20to%20work%20like%20before%20If%20you%20have%20any%20auto%20attendants%20or%20call%20queues%20left%20in%20the%20legacy%20admin%20portal%2C%20they%20will%20be%20fixed%20by%20the%20service%20and%20migrated%20to%20the%20Teams%20Admin%20Portal.%20However%2C%20If%20they%20are%20associated%20with%20an%20on-premises%20resource%20account%2C%20there%20is%20an%20action%20you%20need%20to%20take.%20Check%20out%20the%20section%20How%20to%20fix%20my%20hybrid%20apps%20You%20can%20no%20longer%20use%20the%20legacy%20portal%20to%20create%20new%20application%20instances%20Previous%20application%20instances%20do%20not%20need%20to%20be%20licensed%2C%20and%20will%20continue%20to%20work%20as%20is%20New%20application%20instances%20will%20require%20the%20creation%20of%20a%20Resource%20Account%2C%20licensing%20it%2C%20and%20associating%20it%20with%20your%20application%20instance.%20Only%20resource%20accounts%20with%20a%20phone%20number%20need%20to%20be%20licensed.%20Update%3A%26nbsp%3Ba%20%240%20application%20license%20(Phone%20System%20-%20Virtual%20User)%20can%20be%20acquired%20and%20assigned%20to%20these%20resource%20accounts.%20NOTE%3A%20please%20note%20that%20the%20know%20issue%20listed%20below%20(Removing%20phone%20system%20license%20corrupts%20the%20resource%20accounts)%20is%20still%20not%20resolved.%20To%20avoid%20interruption%20to%20your%20application%2C%20create%20a%20new%20resource%20account%20and%20license%20it%20with%20a%20virtual%20user%20license%2C%20associate%20it%20with%20the%20application%20and%20then%20switch%20the%20phone%20number%20to%20it.%26nbsp%3B%3CP%3EYou%20can%20find%20the%20latest%20updates%20on%20the%20new%20admin%20experience%20and%20capabilities%20in%20the%20updated%20documentation%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FMicrosoftTeams%2Fcreate-a-phone-system-auto-attendant%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3ESet%20up%20a%20Cloud%20auto%20attendant%3C%2FA%3E%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FMicrosoftTeams%2Fcreate-a-phone-system-call-queue%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3ECreate%20a%20Cloud%20call%20queue%3C%2FA%3E%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FMicrosoftTeams%2Fmanage-resource-accounts%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EManage%20resource%20accounts%20in%20Microsoft%20Teams%3C%2FA%3E%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2FMicrosoftTeams%2Fknown-issues%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%20target%3D%22_blank%22%3EKnown%20issues%20for%20Microsoft%20Teams%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKnown%20Issues%20with%20resource%20accounts%3C%2FP%3E%20%3CP%3ESymptom%3C%2FP%3E%20%3CP%3EMitigation%3C%2FP%3E%20%3CP%3EIssue%20Description%3C%2FP%3E%20%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20AA%2FCQ%20is%20not%20functional%3C%2FP%3E%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Not%20able%20to%20assign%20a%20phone%20number%3C%2FP%3E%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20You%E2%80%99re%20getting%20a%20message%20%E2%80%9Cthe%20following%20application%20instance%20is%20not%20present%20in%20BVD%E2%80%9D%3C%2FP%3E%20%3CP%3EAllow%2024h%20sync.%20If%20it%20has%20been%20already%2024h%2C%20make%20sure%20you%20remove%20the%20phone%20number%20assignment%20then%20delete%20the%20RA%2C%20and%20create%20a%20new%20one%20with%20a%20different%20name.%3C%2FP%3E%20%3CP%3Eresource%20accounts%20Sync%20Delay%3C%2FP%3E%20%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Cannot%20change%20phone%20number%3C%2FP%3E%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20You%E2%80%99re%20getting%20an%20error%20%E2%80%9CCannot%20sync%20to%20BVD%E2%80%9D%3C%2FP%3E%20%3CP%3EUse%20Cmdlet%20instead%20of%20the%20portal%3C%2FP%3E%20%3CP%3EDepartment%20parameter%20is%20not%20set%20properly%3C%2FP%3E%20%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Cannot%20assign%20a%20toll-number%20(service%20number)%20from%20admin%20portal%3C%2FP%3E%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Admin%20portal%20returning%20error%20%E2%80%9Cyou%20need%20a%20phone%20system%20license%E2%80%9D%3C%2FP%3E%20%3CP%3EUse%20Cmdlet%20to%20do%20that%3C%2FP%3E%20%3CP%3EAdmin%20Portal%20have%20an%20issue%20with%20toll-number%20assignment%2C%20and%20its%20returning%20the%20wrong%20error%20message%3C%2FP%3E%20%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Admin%20portal%20returning%20error%20%E2%80%9CCall%20Handler%E2%80%A6%E2%80%9D%3C%2FP%3E%20%3CP%3EResource%20account%20is%20not%20synced%2C%20or%20corrupted.%20Wait%20for%20it%20to%20sync%20or%20create%20a%20new%20one.%3C%2FP%3E%20%3CP%3EWrong%20error%20message%3C%2FP%3E%20%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Resource%20account%20not%20working%3C%2FP%3E%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20SIP%20URI%20disappears%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%20%3CP%3ECreate%20a%20new%20RA%20with%20a%20different%20SIP%20URI%20name%3C%2FP%3E%20%3CP%3ERemoving%20phone%20system%20license%20corrupts%20the%20resource%20account.%20Creating%20a%20new%20one%20with%20the%20same%20SIP%20URI%20will%20not%20work%3C%2FP%3E%20%3CP%3E-%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Phone%20number%20blocked%3C%2FP%3E%20%3CP%3EContact%20MS%20to%20release%20the%20TN%3C%2FP%3E%20%3CP%3EDeleting%20the%20resource%20account%20before%20removing%20the%20TN%20will%20block%20the%20phone%20number.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20to%20fix%20my%20hybrid%20application%20instances%3C%2FP%3E%3CP%3EIf%20you%20still%20see%20one%20of%20more%20application%20instances%20in%20the%20legacy%20admin%20portal%2C%20that%20is%20because%20they%20need%20to%20be%20fixed%20in%20your%20hybrid%20environment%2C%20which%20we%20cannot%20do%20on%20your%20behalf.%20Once%20you%20fix%20them%2C%20they%20will%20be%20migrated%20automatically%20within%20a%20week%20to%20the%20Teams%20Admin%20Portal.%20To%20fix%20these%20application%20instances%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%20Log-into%20Skype%20for%20Business%20Online%20PowerShell%3C%2FP%3E%3CP%3E2.%20Run%20the%20following%20Cmdlet%20to%20return%20all%20auto%20attendants%20that%20were%20left%20behind%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGet-CsOrganizationalAutoAttendant%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E3.%20Run%20the%20following%20Cmdlets%20for%20each%20auto%20attendant%20instance%20to%20get%20the%20error%20message%20associated%20with%20it%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EExample%3A%3C%2FP%3E%3CP%3EGet-CsOrganizationalAutoAttendant%20-Tenant%20%3CTID%3E%20-PrimaryUri%20sip%3Aoaa_%20fef4f2df1ef444428ce5760bba2434d2%40contoso.com%3C%2FTID%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EError%20message%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWARNING%3A%202019%2F05%2F03%2002%3A21%3A59%2CDB42E00TAD02%2CWarning%2CActive%20Directory%20object%20used%20for%20locating%20the%20organizational%20auto%20attendant%20(sip%3Aoaa_1c301d33aa4f4d3da911684a17055e48%40contoso.com)%20needs%20to%20be%20created.%20If%20you%20have%20not%20already%20done%20so%2C%20please%20execute%20the%20following%20cmdlet(s)%20on-premises%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENew-CsHybridApplicationEndpoint%20-ApplicationId%20ce933385-9390-45d1-9512-c8d228074e07%20-DisplayName%20%22AA1%22%20-SipAddress%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Esip%3Aoaa_1c301d33aa4f4d3da911684a17055e48%40contoso.com%20-OU%20%5BA_VALID_OU%5D%20-LineUri%20tel%3A%2B4051112222%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E4.%20Follow%20the%20instructions%20from%20the%20error%20message%20and%20run%20the%20New-CsHybridApplicationEndpoint%20Cmdlet%20in%20your%20on-premises%20environment%3C%2FP%3E%3CP%3E5.%20Allow%20up%20to%2024%20hours%20for%20the%20objects%20to%20sync%20with%20AAD%3C%2FP%3E%3CP%3E6.%20To%20verify%20that%20the%20application%20instance%20was%20fixed%2C%20re-run%20the%20Cmdlet%20in%20step-3%20to%20make%20sure%20no%20error%20messages%20are%20returned.%3C%2FP%3E%3CP%3E7.%20Repeat%20steps%203-6%20for%20each%20application%20instance%3C%2FP%3E%3CP%3E8.%20For%20call%20queues%2C%20running%20the%20Get%20Cmdlet%20will%20return%20all%20application%20instances%20errors%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGet-CsHuntGroup%20-Tenant%20470d77bf-25be-42ca-9ed4-ff30831837f4%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWARNING%3A%202019%2F05%2F03%2002%3A36%3A06%2CBL20A00TAD06%2CWarning%2CAttention%3A%20HuntGroup%20configuration%20is%20not%20complete.%20In%20order%20to%20complete%20HuntGroup%20configuration%2C%20you%20must%20also%20run%20corresponding%20on-premises%20commands%20to%20create%20the%20relevant%20object(s)%20in%20your%20on-premises%20topology.%20Please%20copy%20and%20paste%20the%20below%20commands%20and%20run%20them%20in%20your%20on-premises%20Skype%20for%20Business%20environment%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENew-CsHybridApplicationEndpoint%20-ApplicationId%2011cd3e2e-fccb-42ad-ad00-878b93575e07%20-DisplayName%20%22Itentive%20Support%22%20-SipAddress%3C%2FP%3E%3CP%3Esip%3Ahg_f6e68f465a2e4f6fa92ab68493fff1de%40contoso.com%20-OU%20%5BA_VALID_OU%5D%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-564521%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20service%20updates%20for%20Auto%20Attendant%20and%20Call%20Queues%20were%20completed%20successfully%20this%20week.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-564521%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft

Service update notification

The service updates for Auto Attendant and Call Queues were completed successfully this week. The updates introduce new capabilities, namely:

 

1. Centralized holiday tables that can be reused across apps. You will find it under Org wide settings

2. You can assign Direct Routing numbers to Auto Attendant and Call Queues (as of today DR with AA/CQ support Teams users only)

3. You can assign a hybrid number to AA/CQ (OPCH Released 6/17, CCE is still in public preview)

4. You can assign Multiple numbers to an auto attendant or call queue

5. Round Robin routing option is introduced in call queues

 

The updates prepare the services as well for the upcoming features:

6. Transfer out to PSTN from auto attendant and call queues

7. Extension dialing from auto attendant

8. Voicemail shared mailbox for auto attendant and call queues

 

What to expect after the service update?

  • You can now create auto attendants and call queues in Teams Admin Portal
  • Your previous auto attendants and call queues were migrated to Teams Admin portal, and they should continue to work like before
  • If you have any auto attendants or call queues left in the legacy admin portal, they will be fixed by the service and migrated to the Teams Admin Portal. However, If they are associated with an on-premises resource account, there is an action you need to take. Check out the section How to fix my hybrid apps
  • You can no longer use the legacy portal to create new application instances
  • Previous application instances do not need to be licensed, and will continue to work as is
  • New application instances will require the creation of a Resource Account, licensing it, and associating it with your application instance. Only resource accounts with a phone number need to be licensed. Update: a $0 application license (Phone System - Virtual User) can be acquired and assigned to these resource accounts. NOTE: please note that the know issue listed below (Removing phone system license corrupts the resource accounts) is still not resolved. To avoid interruption to your application, create a new resource account and license it with a virtual user license, associate it with the application and then switch the phone number to it. 

You can find the latest updates on the new admin experience and capabilities in the updated documentation:

Set up a Cloud auto attendant

Create a Cloud call queue

Manage resource accounts in Microsoft Teams

Known issues for Microsoft Teams

 

Known Issues with resource accounts

Symptom

Mitigation

Issue Description

-          AA/CQ is not functional

-          Not able to assign a phone number

-          You’re getting a message “the following application instance is not present in BVD”

Allow 24h sync. If it has been already 24h, make sure you remove the phone number assignment then delete the RA, and create a new one with a different name.

resource accounts Sync Delay

-          Cannot change phone number

-          You’re getting an error “Cannot sync to BVD”

Use Cmdlet instead of the portal

Department parameter is not set properly

-          Cannot assign a toll-number (service number) from admin portal

-          Admin portal returning error “you need a phone system license”

Use Cmdlet to do that

Admin Portal have an issue with toll-number assignment, and its returning the wrong error message

-          Admin portal returning error “Call Handler…”

Resource account is not synced, or corrupted. Wait for it to sync or create a new one.

Wrong error message

-          Resource account not working

-          SIP URI disappears

 

Create a new RA with a different SIP URI name

Removing phone system license corrupts the resource account. Creating a new one with the same SIP URI will not work

-          Phone number blocked

Contact MS to release the TN

Deleting the resource account before removing the TN will block the phone number.

 

How to fix my hybrid application instances

If you still see one of more application instances in the legacy admin portal, that is because they need to be fixed in your hybrid environment, which we cannot do on your behalf. Once you fix them, they will be migrated automatically within a week to the Teams Admin Portal. To fix these application instances:

 

1. Log-into Skype for Business Online PowerShell

2. Run the following Cmdlet to return all auto attendants that were left behind

 

Get-CsOrganizationalAutoAttendant

 

3. Run the following Cmdlets for each auto attendant instance to get the error message associated with it:

 

Example:

Get-CsOrganizationalAutoAttendant -Tenant <tid> -PrimaryUri sip:oaa_ fef4f2df1ef444428ce5760bba2434d2@contoso.com

 

Error message:

 

WARNING: 2019/05/03 02:21:59,DB42E00TAD02,Warning,Active Directory object used for locating the organizational auto attendant (sip:oaa_1c301d33aa4f4d3da911684a17055e48@contoso.com) needs to be created. If you have not already done so, please execute the following cmdlet(s) on-premises:

 

New-CsHybridApplicationEndpoint -ApplicationId ce933385-9390-45d1-9512-c8d228074e07 -DisplayName "AA1" -SipAddress

 

sip:oaa_1c301d33aa4f4d3da911684a17055e48@contoso.com -OU [A_VALID_OU] -LineUri tel:+4051112222

 

4. Follow the instructions from the error message and run the New-CsHybridApplicationEndpoint Cmdlet in your on-premises environment

5. Allow up to 24 hours for the objects to sync with AAD

6. To verify that the application instance was fixed, re-run the Cmdlet in step-3 to make sure no error messages are returned.

7. Repeat steps 3-6 for each application instance

8. For call queues, running the Get Cmdlet will return all application instances errors

 

Get-CsHuntGroup -Tenant 470d77bf-25be-42ca-9ed4-ff30831837f4

 

WARNING: 2019/05/03 02:36:06,BL20A00TAD06,Warning,Attention: HuntGroup configuration is not complete. In order to complete HuntGroup configuration, you must also run corresponding on-premises commands to create the relevant object(s) in your on-premises topology. Please copy and paste the below commands and run them in your on-premises Skype for Business environment:

 

New-CsHybridApplicationEndpoint -ApplicationId 11cd3e2e-fccb-42ad-ad00-878b93575e07 -DisplayName "Itentive Support" -SipAddress

sip:hg_f6e68f465a2e4f6fa92ab68493fff1de@contoso.com -OU [A_VALID_OU]

159 Comments
Microsoft

@Mark Linman there was an issue overnight that caused opt-in/out problems for some tenants, it was resolved already and the fix rollout will be completed in couple of hours. 

Visitor

@Waseem Hashem We are having issues with the amount of time a call is held in a Call Queue before being transferred. We have the maximum time set to 15 seconds, but the call is being held for 70 seconds. This is unacceptable. We have a ticket already opened for this issue, but it has not been taken care of. Ticket # 13441387.

Senior Member

Holiday AA issues.jpg
We can not change the time of the day the announcement will start. We want to start at 3:00 PM EST tomorrow. How to change it?

Occasional Contributor

@Waseem Hashem I'm still waiting on a response from you. I'd like to know what product development team approved this botched/forced chnage? Whatever happened to beta testing and ensuring QC before releasing out to production? 

New Contributor

@Waseem Hashem I know the assigning of a hybrid number is still "public preview" so maybe that is still the issue but I still can't get this to work at all. Seems like some people have gotten it to work somewhat but for me nothing about it works. I did have a ticket in but at that time I believe it was still just preview and they said to wait.

 

 

New Contributor
@Toyuwa_Harris It looks like you have to use the "Holidays" table located under the "Org-wide settings" menu option to set the date/time. Can I ask you which action you plan on using in your holiday setup? Disconnect or redirect? I have been arguing since day one of the new auto attendant (almost 1 year ago) that the holiday feature is worthless because the actions are too limited. Hang up on the caller? Redirect to a specific user? I have yet to receive any reply from Microsoft on any of my posts. Crickets...
Senior Member

Our call queues now timeout right at 60 seconds which is an improvement from the 90-120 seconds from before, but I really hope that's not the "fix"  The call queue is set to Timeout at 15 seconds.  If you remove the call agents, it times out right at 15 seconds.  If I change the timeout to 90 seconds, it takes almost 2 minutes to timeout.  There are some upcoming features I'm excited about, but it's getting tough explaining to management these recurring hiccups.

Occasional Contributor
Is anyone having an issue where it doesn't timeout to voicemail?
Visitor

@Jeffrey Bladow we have been dealing with the same issue before the move to Teams. It is very frustrating that Microsoft seems not to care.

Occasional Contributor
@Jeffrey Bladow - you guys seem to have timeout issues, but does it actually time out to a person in your organization / voicemail? With the CQ that migrated over to Teams we can't get the timeout to actually hand off to the voicemail we need.
Microsoft

@Jeffrey Bladow  I mentioned you in a comment on Tuesday regarding the timeout issue, the bug was fixed and rolling out started 2 days ago, and expected to cover all customers by tomorrow. 

Microsoft

@Mike Dominik we are rolling out new features that can be used for holiday treatment, they are listed above in this blog (Transfer to PSTN, Voicemail). Would appreciate your feedback on what else would you expect to have as a holiday treatment?

Microsoft

@jguel  if you post the process you followed or the error you're getting perhaps someone in the community can help?

Microsoft
@Edmundo Pena the changes were tested and validated with customers through the validation program for 3 months, and rollout was controlled by quality, which is why it took 1.5 months to complete the rollout. Unfortunately some of the bugs were not discovered until after the service was made generally available. To your question on the team, I'm the product owner for these services, and I do apologies on behalf of the team for the inconveniences that impacted your business. If you have an outstanding issue that is not resolved please open a support ticket, or contact GetHelp if you want to file an escalation.    
Occasional Visitor

In an auto attendant with menu is there a way to have it default to a particular menu item if the user doesn't choose something.

 

Hi you have reached XYZ company.  Press 1 or just wait to continue in english or press 2 to continue in french.  These would then flip to the appropriate AA for each language.  Just as an example

Contributor

 

@Waseem Hashemthanks for sharing your feedback on the community. I'm running into the issue, that I can't assign available phonenumbers to resourceaccounts. I was able to, 2 days ago, but yesterday I can't anymore. I've assigned a E1+phone system+calling plan subscription to the resource account.  Any idea 🤷‍:male_sign: (subsciptions assigend 24 hours ago)
Found the issue using PowerShell. The numbers I have, seem to be assigned, but can't unassign them (yet). Perhaps a time related issue. I will check it after 24 hours.
Fixed using: Set-csonlinevoiceapplicationinstance -identity <Resource Account oid> -TelephoneNumber $null

002.PNG001.PNG

Occasional Contributor

@Waseem Hashem the service is broken. This is a product development issue. You and your developers have to fix this mess. What do you expect the support team to do other  than act as a punching bag at this point? The support team has already informed me about the proposed licensing work around to address the AA/CQ issues as most people have detailed on this forum. This is not an acceptable solution. This is more than an inconvenience. This type of forced improperly vetted "feature" roll affects end-user customers and partners alike. What is it going to take to make Microsoft to realize these types of rushed implementations cause productivity and monetary issues for customers and reflect negatively on the partners that sell, implement and support Microsoft products. As the product manager you have failed us and this community. This type of work is unacceptable and is prime example of everything that is wrong with cloud services today.

New Contributor
I would expect at the very least that the migration to the new interface (from old UM) would maintain same features as the previous system. With UM, the auto attendant would just kick into after hours mode when a holiday is scheduled. Here's a link to the documentation for the old UM auto attendant. It states that the system will kick over to the after hours business system: https://docs.microsoft.com/en-us/exchange/voice-mail-unified-messaging/automatically-answer-and-rout... I appreciate giving the users a choice (the old system only went to after hours) but I find it hard to believe that the choices provided (disconnect or redirect to another auto attendant) are preferred by anyone over the original after hours approach. As it is now, the system is unusable and I still have to just change my business hours and greeting for every holiday. I have been anxiously waiting for the voicemail option (also available in the old system) because I have had to create 5 separate accounts (consuming licenses) AND setup Flow tasks for each just to simulate a shared voicemail box.
Microsoft

thanks @Mike Dominik  for the feedback, totally agree. The holiday logic in auto attendant need to be revisited, and current options are not sufficient. What we want to do is fix the logic (more like reverse it), and add PSTN transfer and Voicemail to the Transfer and Disconnect options. Can you elaborate more please on this statement " I still have to just change my business hours and greeting for every holiday"? 

Microsoft

Question to Everyone: did anyone have to go through the process in the blog to fix hybrid resource accounts? would appreciate your feedback on that. 

New Contributor
Let's take this weekend for example. We are closed from 5/24 at 3pm through Monday all day for Memorial Day. We want to play a special message (holiday greeting) and then roll into the after hours menu. My current process is to change my business hours so we are closed during that period of time and then replace the After Hours greeting to be a special message. On Tuesday, I have to log back in, reset the hours and put the greeting back (I have forgotten to do this before). What I would like is for the holiday setup to just roll into the after hours so I don't have to do this. It would just play the holiday message and then treat the business as being closed.
Contributor

@Waseem Hashemsorry, we ar cloud only, no hybrid.

Occasional Contributor
I see here that there will be another unwanted change foisted on us in the near future: https://docs.microsoft.com/en-us/DeployOffice/teams-install Part way down the page this says that not only will the Teams client be part of *new* office installs (understandable and easily dealt with by excluding it) but that you'll actually be quietly be sneaking the Teams client into *EXISTING* installs when they're updated. Unsurprisingly the doc doesn't go into any details about methods to rerun the ODT /configure on existing clients, nor does it say what that client experience is going to be like. Will there be interaction required? Will users get strange popups/warnings that will lead to helpdesk impact? Will they be unable to launch office apps while this update is occurring?
New Contributor

Hello,

I am facing issues with the AA/CQ with direct routing. From the configuration point of view all went well as per the documentation.  I receive an SIP error code from the CCE (mediation) "480"

Resource Account created for AA/CQ, assigned the E1 and Phones system license.

Phone number assigned using Powershell for direct routing for this resource account.

AA/CQ configured to use the repective resource account.

 

Calls from the SIP trunk lands on the SBC and routed to CCE (Mediation), response from the cloud back via the CCE to the SBC shows an error code of 480 (temprarily unaavailable)

 

Occasional Contributor

Direct Routing only works with Teams. CCE works based on federation. 

New Contributor
 
 : I tried routing this call via Teams interface now and now receive an error code of 404 from MS cloud.   Not sure if it takes the cloud changes to propogate and takes 24 hours or it is some other kind of issue.
 

 

Occasional Contributor

@Thangavel MudaliarI'm also seeing SIP/2.0 480 Temporarily Unavailable errors in relation to our Skype/Exchange hybrid environment, specifically Exchange Online UM. We have a group of people using Skype onprem + Exchange Online + Exchange Online UM for voicemail and calls are consistently not working to the Outlook Voice Access number, and inconsistently not timing out to their voicemail box.

 

I have to think some of these Exchange Online UM + Cloud Voicemail + Phone System errors are related.

Occasional Contributor
@Thangavel Mudaliar Yeah 404 normally relates to replication. In my case it took nearly 3 days before it kicked in.
Senior Member

Has anybody tried out the new feature : "Assign a hybrid number to AA/CQ (in public preview)" ? I have trying to create an on-premise resource account via the cmdlet "New-CsHybridApplicationEndPoint". We clearly see that the account is created in Office365, but can't assign it to a AA/CQ, as we can only assign Cloud Resource Accounts to a AA/CQ. We are stuck at the moment as we can't create anymore AA/CA in our Skype for Business 2015 Hybrid environment.

New Contributor

@Philip De Graef

 

I have not been able to do this either.

 

Steps I took:

1. Online powershell ran new-csonlineapplicationendpoint

2. On-premises powershell ran new-cshybridapplicationendpoint per the output of #1

3. Assigned the on-premises endpoint a DID number using set-csybridapplicationendpoint in on-premises powershell

4. After AD Sync assigned the account phone system, teams, and skype for business license

5. Resource account shows up under Teams Admin Portal under Org Wide Settings->Resource accounts

6. Within the call queue go to assign a resource account and it does not show up so..

7. Go to the resource account and under Assign/Unassign I'm able to assign it to a call queue there

8. Go back to call queue and see the resource account is assigned - wait some time for replication

9. Call the number - all I get is ringing and on-premises shows nothing in the trace logs.

 

New Contributor

@Waseem Hashem Call Queues and auto attendant management is down again.... Reopened case 14334892

https://admin1e.online.lync.com/OcsPowershellWebservice/Service.svc/V1_AutoAttendant?First=20&Includ...> HTTP/1.1 Host: admin1e.online.lync.com HTTP Error 503. The service is unavailable.

 

Occasional Visitor
@Waseem Hashem: I am trying to redirect my call from Auto Attendant to a Call Queue. The Call Queue is created and I have added a Resource Account for both CQ and AA. But when I trying to find the CQ from Voice App list its not showing. I tried to add the Resource Account instead which is searchable but when I am submitting its giving me a error "Error We can't create call handler at the moment." Can you please let me know how we can do the redirection from a AA to a CQ. Thanks Avijit Chakraborty
Frequent Visitor

I have been eagerly awaiting the Call Queue and Auto Attendant feature in Teams for probably well over a year as I have had customers working with 'post-it notes' on their Polycom VVX phones to allow them to identify incoming calls to queue calls as the TOAST showed only the GUID (according to MS it wasn't worth fixing in SfB and will be in Teams).

 

Now however I can't even seems to associate a number with said CQ or AA?

 

Does this stuff in anyway get a quality and/or even a basic functionality check before passing out into production? What's the most irritating is that none of this seems to be communicated - indeed the title of this post 'The service updates for Auto Attendant and Call Queues were completed successfully this week' but no-where does it then go on to say - apart from the most basic part of setting up a call queue (as in giving it a number) doesn't actually work!?!

 

I have raised tickets - always to no avail. I'm getting a bit fed up of looking the plonker here - and the good old trusted PBX in the corner might have to be dusted off and brought back into play. 

 

 

Senior Member

This is totally unacceptable, I have just started work to move our entire organisation to the cloud PBX system but now through the rollout of a new user interface you require us to purchase licences for Auto Attendants until you fix the problem you have created? In that case are you going to refund us for the additional licences we now 'temporarily' require while you fix this?

 

At the moment we have halted our migration until this is resolved. I have raised a support ticket, but I know they are unlikely to be able to help at this point.

Occasional Contributor

@Waseem Hashem Any idea when we will see some respite from this train wreck of a "FeaTuRe UpDate"?

Regular Visitor

UPDATE: 05/30/19 - 1:42PM EST - Port team (ptn@microsoft.com) just emailed me back per an email I sent to them earlier today.  I requested the main "published" telephone number be converted from a "service" number back to a "user" number.  Logged into the Teams Admin Center and clicked on the Legacy Portal and was able to successfully assign the number to one of our end users.  We now at least have one phone set ringing in with our main "published" telephone number.  Decent temporary Band-aid.  Would have done that days ago had support tech known of such problem existed.

 

 

@Waseem HashemI've stumbled upon this thread today while searching for a fix for a client who has now been without inbound phone service on their main "published" telephone number for +48 hours.

 

We built out their "Phone System" several weeks ago; assigned users numbers, reconfigured phones on all desks, got them outfitted with dial tone, built out their auto attendant with a temporary service number assigned, etc.  We then contacted their existing carrier to forward their main "published" telephone number to the temporary number we had assigned to the auto attendant.  Everything went great.  Had them migrated to Microsoft and fully operational in a matter of hours with no downtime.  We then placed our port order on 05/21/19 for their main "published" telephone number, which happened to be the only telephone number we needed from their existing carrier since it was the only "published" telephone number for this business.

 

Tuesday morning, 05/28/19, as scheduled, their main "published" telephone number ported to Microsoft.  Based on everything discussed in this entire thread, what do you think happened next?????

 

Yep!  Microsoft now has possession of our client's "ONLY" and main "PUBLISHED" telephone number and it can't be assigned to not only the auto attendant we created, but ANY auto attendant or call queue we try to build.

 

I've personally worked with support for almost 48 hours and they've been able to fix nothing, nor did they bother to even elude to any such known issue (internal communication problem inside Microsoft or stall tactic?).  Instead they've spun my wheels for 2 days.  This morning, our client started day 3 of the work week with still no inbound calling to their main "published" telephone number with inbound callers being told the number is "NOT IN SERVICE!"  They are essentially on day 3 of no business...and my company looks like a bunch of A**HOLES since it was our brilliant idea to migrate them to Microsoft.

 

Before, during and after the port, there was NEVER any disclaimer that stated in ANY way that in the event we were an organization attempting to port in numbers that would be designated as service numbers, that were to be assigned to necessary account objects, that there would be ANY issue in doing such.  HOWEVER, this thread is over 2 weeks old and there appears to still be no resolution in sight.

 

1.  What is the fix for our client...what is the time table to resolution?  Do we place another port order with another carrier to temporarily port the number away from Microsoft so they can forward it to one of our end-user's user numbers?  We need a fix yesterday and support is dragging their butts on providing one.

 

2. Why in God's name were we not warned of the problem by the port team BEFORE, DURING or AFTER the port order was placed?  This issue is weeks old.  If there is such a known problem, why has the port team not put a halt or disclaimer on porting service numbers in from other carriers?  You are essentially dismantling and handcuffing clients in such scenarios as I have described.  If by chance you're still porting in (service) numbers from other carriers that need to be assigned, STOP IT!

 

Please write back providing a reasonable pathway to resolution.  Our client needs to be back in business.

 

Michael Lawrence

New Contributor

I hope this helps everyone in this post including Michael above.  We went through the exact same thing, ported our only number required the weekend of the original AA and Call Queue Migration and still do not have proper control over service numbers in teams portal and it is gone in Legacy portal.  The fix for us ended up being a simple thing but hard to find, since all our resource accounts, AA, and Call queues were already done when MS did migration.  The fix is simply do not use exisiting resource accounts and all commands have to be done in Powershell that is documented in MS article.  So make new resource account in powershell, assign licenses to the resource account, then assign number to resource account in powershell.  then you can assign the resource account to your auto attendant in teams admin portal.  Below is the article that has all the required commands.

 

https://docs.microsoft.com/en-us/microsoftteams/manage-resource-accounts

 

 

 
 
Occasional Contributor

Days in and still unable to get key presses working on our new AA.  Pathetic.

Senior Member

"What to expect after the service update?

  • You can now create auto attendants and call queues in Teams Admin Portal
  • Your previous auto attendants and call queues were migrated to Teams Admin portal, and they should continue to work like before"

Unless you need to make a change like change a number on an Auto-Attendant. Then you have to license/pay up until the hopeful July free licensing if you want to save the change.

 

For the sake of two months of new features could this have been delayed (and tested and refine a little more) two months and scheduled at the same time?

Frequent Visitor

@Robert_Hurd thanks for the tip however in my case I get;

 

Set-CsOnlineVoiceApplicationInstance -Identity name@mydomain.com -TelephoneNumber +myservicenumber

 

WARNING: The following Application Instance not present in BVD: [string]

Senior Member

An update from Microsoft support regarding the Auto Attendant Licencing 'requirements':

 

They explained to me that they have received many complaints about the issue but are powerless to do anything to help (as I guessed). They agree that from a customer point of view what has happened here is very poor and encourage us to make our views clear on the user voice website.

 

They also encouraged me to share the following link and get anyone in the same position to vote and comment to move it up their priority lists...

 

https://microsoftteams.uservoice.com/forums/555103-public/suggestions/37694869-call-queue-and-auto-a...

New Contributor

@Paul Coward  did you create the resource account by using the 

New-CsOnlineApplicationInstance -UserPrincipalName testra1@contoso.com -ApplicationId “ce933385-9390-45d1-9512-c8d228074e07” -DisplayName "Resource account 1"

Command?  I was getting exactly the same thing until i i created the new resource account within powershell.  I am guessing this is what you have tried and it has just broken more for people since the may 05 weekend when this all started.  Let me know and.i will help how i can.  I really hope you have not tried this and this works for you.  I am also amazed how this has gone and i at least hope Ms learns from this as Thia has been handled and communicated very poorly.  @Paul Coward did you assign the calling plan and communication credit license after you create resource account?

The application ID's that you need to use while creating the application instances are:

 

Auto Attendant: ce933385-9390-45d1-9512-c8d228074e07

Call Queue: 11cd3e2e-fccb-42ad-ad00-878b93575e07

 

Senior Member

Using Common Area Phone License bundle + a Call plan, to license a AA/CQ resource account requiring PSTN number assignment, seems to work and be cheaper than E1 + call plan.
Note sure why Microsoft doco doesn't suggest that in interim until they have new AA/CQ Licensing released in July (hopefully sooner not later).

 

Also note, that assigning multiple numbers to a single Auto-Attendant/Call-Queue is done by assigning each number to a single resource account, which are then assigned to an AA/CQ, each resource account will need to be licensed at this stage .

Senior Member

Had an issue where an auto-attendant that was migrated to Teams portal needed it's number changed. So I had to license the resource account to be enabled to list and assign the desired PSTN number, it would save it saved successfully and display in list correctly, but not work. after checking the number in SfB portal I noticed the number was listed but not assigned. going back to teams portal window and refreshing resource accounts list, the list would then reveal that the PSTN number assignment had reverted back to original PSTN number. Tried same process again with same result. I had to create a new resource account, transfer licenses to successfully update the AA PSTN number. So another GUI bug for the Teams team to resolve.

Microsoft

Hi @Wes Lazara - I'm following up on your post from May 24, about Microsoft Teams coming to existing installations of Office 365 ProPlus, and am happy to address your concerns.

Part way down the page this says that not only will the Teams client be part of *new* office installs (understandable and easily dealt with by excluding it) but that you'll actually be quietly be sneaking the Teams client into *EXISTING* installs when they're updated.
We posted this to the Message Center, as well as the Microsoft 365 Roadmap, but posting about it here, as you've done, is another great way to inform people.  Thank you!

 

Unsurprisingly the doc doesn't go into any details about methods to rerun the ODT /configure on existing clients, nor does it say what that client experience is going to be like.  In the Docs.Microsoft.Com article you mentioned above, about halfway down the page, is this information about running ODT in the /configure mode to exclude the Teams app from installing on computers that already have Office 365 ProPlus installed - we could probably add an anchor to that part of the documentation, to make it easier to find and link to: "If you don't want Teams to be added to existing installations of Office 365 ProPlus when you update to a new version, use the Office Deployment Tool and the following configuration.xml. You need to run the Office Deployment Tool in /configure mode on each device before you update to the new version."

 

Will there be interaction required? Will users get strange popups/warnings that will lead to helpdesk impact? Will they be unable to launch office apps while this update is occurring?

Those are great questions.  The Teams desktop app will install as part of an Office 365 ProPlus update, so the experience doesn't vary from that.  This article describes the end-user experience for Office 365 ProPlus updates, and this article provides an overview of the update process.

 

Thanks again for your feedback, and I hope you find the information in this response helpful.

Steve

Occasional Contributor

Hey @Steve Conn  , thank you for the update!  What you've already mentioned here is helpful and I think the doc updates you suggest would be welcome.  As for the question about interaction/popups/warning/etc, I was referring not to the typical behind-the-scenes update process during which Teams will roll out...  but rather we are focused on preventing Teams (for now at least) from rolling out to our hundreds of already-deployed c2r proplus machines.  What mechanism is suggested/best practice to actually carry out "the ODT in /configure mode on each device before you update to the new version" ?  And does that suggested mechanism cause/require interaction/popups/warnings etc?

 

Thank you!

Microsoft

@Jef Vleugels seems like you're having a problem with the admin portal, if the ticket is open the portal team will track that with you. 

Microsoft

@Avijit_Chakraborty  you currently search and redirect calls to a resource account instead of a CQ/AA instance. This is something we want to change in the future. the error you mentioned is a know issue on the portal, they are looking at it. if you try using Cmdlets it should work fine. 

Microsoft

@Paul Coward incoming CQ call to an agent on VVX will display the Caller ID and the SIP URI name of the queue. Polycom have completed the fix to change the SIP URI to the given CQ name instead, the new firmware will start rolling out soon. 

New Contributor

Has anyone successfully created a new CQ by creating a new resource account and assigning a hybrid number and the resource account to a CQ and have it actually work?

If so can you share your process?