%3CLINGO-SUB%20id%3D%22lingo-sub-1696499%22%20slang%3D%22en-US%22%3EMigrate%2C%20modernize%20.NET%20applications%20with%20Azure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1696499%22%20slang%3D%22en-US%22%3E%3CP%3EDigital%20demand%20for%20goods%2C%20services%20and%20information%20has%20never%20been%20higher%20and%20organizations%20of%20all%20sizes%20are%20bringing%20their%20web%20applications%20to%20the%20cloud%20to%20save%20costs%20and%20better%20support%20remote%20employees%2C%20customers%2C%20and%20partners.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20this%20demand%20grows%2C%20many%20of%20our%20customers%20have%20found%20that%20their%20current%20infrastructure%20is%20either%20limited%20in%20capacity%20or%20lacks%20the%20agility%20to%20keep%20pace%20with%20changing%20user%20needs.%20%3CA%20href%3D%22https%3A%2F%2Fcustomers.microsoft.com%2Fen-us%2Fstory%2F754838-premera-blue-cross-health-payor-azure%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EPremera%20Blue%20Cross%3C%2FA%3E%26nbsp%3Bis%20using%20App%20Service%20to%20simplify%20operations%20for%20Premera.com%20and%20protect%20patient%20data.%20%3CA%20href%3D%22https%3A%2F%2Fcustomers.microsoft.com%2Fen-US%2Fstory%2F845185-academy-motion-picture-arts-sciences-media-entertainment-azure%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EThe%20Academy%20of%20Motion%20Picture%20Arts%20and%20Sciences%3C%2FA%3E%26nbsp%3Bmigrated%20their%20apps%20to%20Azure%20to%20rationalize%20legacy%20infrastructure%20costs%20and%20create%20new%20experiences%20for%20their%20members.%20And%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fcitynational%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ECity%20National%20Bank%3C%2FA%3E%20needed%20modern%20CI%2FCD%20tools%20to%20make%20their%20development%20processes%20more%20predictable%2C%20automated%20and%20repeatable.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20class%3D%22lia-indent-padding-left-30px%22%3E%3CEM%3E%E2%80%9CNobody%20understands%20.NET%20and%20SQL%20Server%20better%20than%20Microsoft%2C%20which%2C%20through%20Azure%2C%20gave%20us%20a%20robust%20set%20of%20managed%20services%20for%20migrating%20our%20legacy%20applications%20to%20the%20cloud.%E2%80%9D%3C%2FEM%3E%3C%2FP%3E%0A%3CP%20class%3D%22lia-indent-padding-left-30px%22%3E%3CSTRONG%3EBev%20Kite%2C%20Chief%20Information%20Officer%2C%20Academy%20of%20Motion%20Picture%20Arts%20and%20Sciences%26nbsp%3B%20%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20the%20steward%20of%20Windows%20Server%2C%20SQL%20Server%2C%20.NET%20and%20Visual%20Studio%20for%20the%20past%20two%20decades%2C%20Microsoft%20has%20built%20best%20in%20class%20application%20development%20%26nbsp%3Benvironments%20in%20Azure%20for%20%3CA%20href%3D%22https%3A%2F%2Fazure.microsoft.com%2Fen-in%2Fblog%2Fthree-reasons-to-migrate-your-aspnet-apps-and-sql-server-data-to-azure%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EASP.NET%20web%20apps%20and%20SQL%20databases%3C%2FA%3E.%20In%20fact%2C%20App%20Service%20and%20Azure%20SQL%20were%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fdotnetgigaom%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Erecently%20benchmarked%3C%2FA%3E%20by%20GigaOm%20as%20the%20most%20cost%20effective%20and%20performant%20environments%20to%20run%20ASP.NET%20web%20workloads.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EToday%2C%20we%E2%80%99re%20announcing%20several%20major%20investments%20in%20App%20Service%20designed%20to%20make%20it%20easier%20and%20more%20cost%20effective%20to%20migrate%20and%20modernize%20your%20.NET%20web%20apps%20with%20Azure.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EOur%20most%20performant%3C%2FSTRONG%3E%3CSTRONG%3E%2C%20cost%20effective%20offerings%20ever%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EStarting%20October%201%3CSUP%3Est%3C%2FSUP%3E%2C%20customers%20will%20be%20able%20to%20use%20our%20updated%20Premium%20v3%20(Pv3)%20offering%2C%20which%20leverages%20the%20latest%20Azure%20Dv4%20Virtual%20Machine%20(VM)%20hardware%20to%20deliver%20improved%20performance%20and%20scalability.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENew%202%2C4%2C%20and%208%20vCore%20options%20stretch%20up%20to%2032%20GBs%20of%20memory.%20These%20new%2C%20more%20powerful%20configurations%20can%20handle%20more%20apps%20per%20instance%20and%20better%20support%20the%20large%2C%20enterprise%20applications%20and%20content%20management%20systems%20our%20customers%20use%20to%20run%20their%20most%20critical%20operations.%20With%20more%20competitive%20price%20points%20for%20dev%2Ftest%20and%20production%20workloads%2C%20Premium%20v3%20is%20our%20most%20cost-effective%20and%20performant%20offering%20ever.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22IGNITE%20updated%20table.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F221156iFD5734284A9BF0D0%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22IGNITE%20updated%20table.png%22%20alt%3D%22IGNITE%20updated%20table.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWith%20Premium%20v3%2C%20our%20support%20for%20Windows%20Containers%20also%20becomes%20Generally%20Available%2C%20making%20it%20possible%20for%20a%20variety%20of%20.NET%20applications%20with%20legacy%20configurations%20-%20including%20apps%20using%20COM%2B%2C%20GAC%20and%20those%20with%20custom%20OS%20level%20dependencies%2C%20as%20well%20as%20many%20WCF%20services%20-%20to%20migrate%20to%20Azure%20App%20Service.%20%26nbsp%3BAnd%20for%20the%20first%20time%20on%20App%20Service%20we%20are%20introducing%20Reservations%20Pricing%20to%20help%20customers%20control%20their%20TCO%20and%20better%20manage%20costs.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22IGNITE%20Premium%20Chart.png%22%20style%3D%22width%3A%20930px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F220815iE7755565EF45DD2F%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22IGNITE%20Premium%20Chart.png%22%20alt%3D%22IGNITE%20Premium%20Chart.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EStarting%26nbsp%3BNovember%26nbsp%3B1%3CSUP%3Est%3C%2FSUP%3E%2C%20customers%20can%20save%20up%20to%2035%20percent%26nbsp%3Bwith%20a%201-year%20commitment%20and%26nbsp%3Bup%20to%26nbsp%3B55%20percent%26nbsp%3Bfor%26nbsp%3Ba%26nbsp%3B3-year%20commitment%2C%20compared%20to%20pay%20as%20you%20go%20prices.%26nbsp%3BWe%20are%20also%20extending%20our%20dev%2Ftest%20pricing%20discounts%20to%20Premium%20v3%20as%20well%20as%20Premium%20v2%2C%20making%20it%20more%20affordable%20(%3CA%20href%3D%22https%3A%2F%2Fazure.microsoft.com%2Fen-us%2Foffers%2Fms-azr-0148p%2F%23%3A~%3Atext%3DEnterprise%2520Dev%252FTest%2520is%2520exclusively%2520for%2520development%2520and%2520testing%2Cuse%2520of%2520Visual%2520Studio%2520Team%2520Services%2520and%2520HockeyApp.%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eespecially%3C%2FA%3E%20for%20Visual%20Studio%20subscribers)%20to%20test%20workloads%20that%20require%20VNet%20connectivity%20before%20deploying.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ECost%20savings%20and%20networking%20innovation%20for%20Isolated%20workloads%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20customers%20in%20regulated%20industries%2C%20our%20App%20Service%20Environments%20(ASE)%20provide%20an%20isolated%20environment%20to%20run%20their%20most%20sensitive%20web%20workloads.%20After%20several%20years%20of%20infrastructure%20and%20networking%20investments%2C%20we%20pleased%20to%20share%20that%20our%20App%20Service%20Environment%20v3%20(ASEv3)%20will%20be%20available%20in%20Public%20Preview%20on%20November%201%3CSUP%3Est%3C%2FSUP%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20new%20single%20tenant%20architecture%2C%20built%20on%20Virtual%20Machine%20Scale%20Sets%2C%20places%20customer%20application%20endpoints%20in%20the%20customer's%20virtual%20network%2C%20while%20the%20internal%20ASE%20infrastructure%20is%20deployed%20in%20a%20separate%2C%20Azure%20controlled%20network.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22IGNITE%20ASE%20v2.png%22%20style%3D%22width%3A%20650px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F220816i30538F7DE87F4981%2Fimage-dimensions%2F650x264%3Fv%3D1.0%22%20width%3D%22650%22%20height%3D%22264%22%20title%3D%22IGNITE%20ASE%20v2.png%22%20alt%3D%22IGNITE%20ASE%20v2.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20approach%20eliminates%20any%20ASE%20management%20traffic%20in%20the%20customer's%20network%20and%20vastly%20simplifies%20the%20deployment%20experience.%20This%20new%20ASE%20will%20be%20available%20as%20part%20of%20our%20Isolated%20v2%20App%20Service%20plan%2C%20with%20no%20per%20instance%20stamp%20fee%2C%20offering%20an%2080%25%20reduction%20in%20deployment%20costs%20compared%20to%20Isolated%20v1.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EModernizing%20with%20.NET%205%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMicrosoft's%20commitment%20to%20.NET%20extends%20to%20the%20cloud%20and%20beyond.%20We're%20continuing%20to%20invest%20in%20the%20open%20source%20.NET%20platform%20to%20provide%20experiences%20for%20building%20%26nbsp%3Bacross%20operating%20systems%20and%20devices.%20Today%2C%20the%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fdotnet5%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3E.NET%205%20Release%20Candidate%20is%20available%3C%2FA%3E%20with%20a%20Go-live%20license%20so%20you%20are%20supported%20in%20production.%20This%20release%20continues%20the%20journey%20to%20unify%20the%20platform%20across%20web%2C%20cloud%2C%20desktop%2C%20mobile%2C%20IoT%2C%20machine%20learning%20%26amp%3B%20AI.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20particular%2C%20this%20release%20focuses%20on%20making%20.NET%20the%20most%20productive%20platform%20for%20building%20high-performance%20microservices%20and%20container-based%20applications%20with%20the%20introduction%20of%20single%20file%20applications%2C%20smaller%20container%20images%2C%20and%20smaller%20memory%20footprint.%20It%20adds%20support%20for%20Windows%20ARM64%2C%20contains%20significant%20runtime%20performance%20improvements%2C%20and%20includes%20new%20C%23%209.0%20%26amp%3B%20F%23%205.0%20language%20features.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20ASP.NET%20Core%20web%20stack%20also%20has%20many%20additional%20enhancements%20for%20building%20modern%20web%20applications%20and%20services%2C%20including%20integrated%20Azure%20Active%20Directory%20authentication%20with%20Microsoft.Identity.Web%2C%20Blazor%20%26nbsp%3Benhancements%20like%20CSS%20isolation%20for%20Blazor%20components%2C%20protected%20browser%20storage%2C%20and%20lazy%20loading%20in%20Blazor%20WebAssembly%20for%20improved%20load%20times.%20Blazor%20is%20also%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FBlazorStaticWebApps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Enow%20supported%3C%2FA%3E%20in%20Azure%20App%20Service%20Static%20Web%20Apps.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20can%20learn%20more%20about%20the%20release%20on%20the%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fdotnet5%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3E.NET%20Team%20blog%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EGet%20started%20today%20with%20the%20Azure%20Migration%20Program%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAzure%20is%20the%20home%20for%20.NET%20apps.%20With%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Flearn%2Fpaths%2Fmigrate-dotnet-apps-azure%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Efree%20and%20easy%20to%20use%20migration%20assistants%3C%2FA%3E%20for%20App%20Service%20and%20Azure%20SQL%20and%20new%20streamlined%20resources%20available%20through%20the%20%3CA%20href%3D%22https%3A%2F%2Fazure.microsoft.com%2Fen-us%2Fmigration%2Fmigration-program%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EAzure%20Migration%20Program%3C%2FA%3E%2C%20it%20has%20never%20been%20easier%20to%20save%20costs%20and%20begin%20your%20modernization%20journey!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1696499%22%20slang%3D%22en-US%22%3E%3CP%3EBring%20your%20ASP.NET%20applications%20to%20Azure%20and%20save%2050%25%20or%20more%20vs.%20running%20on-premises%2C%20and%20modernize%20those%20apps%20with%20.NET%205%20and%20new%20Blazor%20support%20in%20Static%20Web%20Apps!%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1696499%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E.NET%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EASP%20.NET%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzure%20App%20Service%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EServerless%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWeb%20Apps%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1703042%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%2C%20modernize%20.NET%20applications%20with%20Azure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1703042%22%20slang%3D%22en-US%22%3E%3CP%3EI%20may%20be%20doing%20it%20wrong%2C%20but%20it%20seems%20like%20to%20achieve%20the%20same%20performance%20in%20a%20Web%20App%20as%20a%20VM%2FIIS%20hosted%20site%20you%20need%20to%20spend%20significantly%20more.%20I%20appreciate%20the%20Azure%20VM%E2%80%99s%20but%20always%20imagined%20that%20I%E2%80%99d%20move%20to%20Web%20Apps%20to%20leverage%20the%20platform%20and%20so%20far%20it%20hasn%E2%80%99t%20made%20sense.%20Hope%20that%20changes%20soon.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1704339%22%20slang%3D%22en-US%22%3ERe%3A%20Migrate%2C%20modernize%20.NET%20applications%20with%20Azure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1704339%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%2F805743%22%20target%3D%22_blank%22%3E%40Jakenuts%3C%2FA%3E%26nbsp%3Bthat's%20a%26nbsp%3Bfair%20observation%2C%20the%20underlying%20machines%20are%20the%20same%2C%20but%20we%20built%20App%20Service%20to%20do%20more%20than%20simple%20hosting.%20It%20is%20a%20fully%20managed%20environment%20for%20building%20and%20managing%20ASP.NET%20web%20apps.%20We%20built%20native%20integrations%20with%20Visual%20Studio%20and%20GitHub%20for%20live%20site%20debugging%20and%20automated%20CI%2FCD.%20We%20created%20deployment%20slots%20so%20you%20can%20ship%20code%20changes%20with%20no%20downtime.%20We%20have%20out%20of%20the%20box%20monitoring%20designed%20specifically%26nbsp%3Bfor%20ASP.NET%20apps%20and%20built%20small%20details%20like%20pre-installing%20URL%20Rewrite%20for%20devs%20to%20define%20custom%20rules%20in%20web.config.%20This%20week%20we%E2%80%99re%20updating%20the%20hardware%20so%20your%20apps%20can%20run%20on%20the%20best%20machines%2C%20and%20lower%20rates%20-%20soon%20with%20commitment%20discounts%20-%20to%20make%20it%20more%20affordable.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

Digital demand for goods, services and information has never been higher and organizations of all sizes are bringing their web applications to the cloud to save costs and better support remote employees, customers, and partners.

 

As this demand grows, many of our customers have found that their current infrastructure is either limited in capacity or lacks the agility to keep pace with changing user needs. Premera Blue Cross is using App Service to simplify operations for Premera.com and protect patient data. The Academy of Motion Picture Arts and Sciences migrated their apps to Azure to rationalize legacy infrastructure costs and create new experiences for their members. And City National Bank needed modern CI/CD tools to make their development processes more predictable, automated and repeatable.

 

“Nobody understands .NET and SQL Server better than Microsoft, which, through Azure, gave us a robust set of managed services for migrating our legacy applications to the cloud.”

Bev Kite, Chief Information Officer, Academy of Motion Picture Arts and Sciences 

 

As the steward of Windows Server, SQL Server, .NET and Visual Studio for the past two decades, Microsoft has built best in class application development  environments in Azure for ASP.NET web apps and SQL databases. In fact, App Service and Azure SQL were recently benchmarked by GigaOm as the most cost effective and performant environments to run ASP.NET web workloads.

 

Today, we’re announcing several major investments in App Service designed to make it easier and more cost effective to migrate and modernize your .NET web apps with Azure.

 

Our most performant, cost effective offerings ever

 

Starting October 1st, customers will be able to use our updated Premium v3 (Pv3) offering, which leverages the latest Azure Dv4 Virtual Machine (VM) hardware to deliver improved performance and scalability.

 

New 2,4, and 8 vCore options stretch up to 32 GBs of memory. These new, more powerful configurations can handle more apps per instance and better support the large, enterprise applications and content management systems our customers use to run their most critical operations. With more competitive price points for dev/test and production workloads, Premium v3 is our most cost-effective and performant offering ever.

 

IGNITE updated table.png

 

With Premium v3, our support for Windows Containers also becomes Generally Available, making it possible for a variety of .NET applications with legacy configurations - including apps using COM+, GAC and those with custom OS level dependencies, as well as many WCF services - to migrate to Azure App Service.  And for the first time on App Service we are introducing Reservations Pricing to help customers control their TCO and better manage costs.

 

RI.png

 

Starting November 1st, customers can save up to 35 percent with a 1-year commitment and up to 55 percent for a 3-year commitment, compared to pay as you go prices. We are also extending our dev/test pricing discounts to Premium v3 as well as Premium v2, making it more affordable (especially for Visual Studio subscribers) to test workloads that require VNet connectivity before deploying.

 

Cost savings and networking innovation for Isolated workloads

 

For customers in regulated industries, our App Service Environments (ASE) provide an isolated environment to run their most sensitive web workloads. After several years of infrastructure and networking investments, we pleased to share that our App Service Environment v3 (ASEv3) will be available in Public Preview on November 1st.

 

This new single tenant architecture, built on Virtual Machine Scale Sets, places customer application endpoints in the customer's virtual network, while the internal ASE infrastructure is deployed in a separate, Azure controlled network. 

 

IGNITE ASE v2.png

 

This approach eliminates any ASE management traffic in the customer's network and vastly simplifies the deployment experience. This new ASE will be available as part of our Isolated v2 App Service plan, with no per instance stamp fee, offering an 80% reduction in deployment costs compared to Isolated v1.

 

Modernizing with .NET 5

 

Microsoft's commitment to .NET extends to the cloud and beyond. We're continuing to invest in the open source .NET platform to provide experiences for building  across operating systems and devices. Today, the .NET 5 Release Candidate is available with a Go-live license so you are supported in production. This release continues the journey to unify the platform across web, cloud, desktop, mobile, IoT, machine learning & AI.

 

In particular, this release focuses on making .NET the most productive platform for building high-performance microservices and container-based applications with the introduction of single file applications, smaller container images, and smaller memory footprint. It adds support for Windows ARM64, contains significant runtime performance improvements, and includes new C# 9.0 & F# 5.0 language features.

 

The ASP.NET Core web stack also has many additional enhancements for building modern web applications and services, including integrated Azure Active Directory authentication with Microsoft.Identity.Web, Blazor  enhancements like CSS isolation for Blazor components, protected browser storage, and lazy loading in Blazor WebAssembly for improved load times. Blazor is also now supported in Azure App Service Static Web Apps.

 

You can learn more about the release on the .NET Team blog.

 

Get started today with the Azure Migration Program

 

Azure is the home for .NET apps. With free and easy to use migration assistants for App Service and Azure SQL and new streamlined resources available through the Azure Migration Program, it has never been easier to save costs and begin your modernization journey!

 

**Note: App Service Premium Monthly Cost chart updated 10/12/20 to reflect the correct reservation prices for US East

40 Comments
Occasional Visitor

I may be doing it wrong, but it seems like to achieve the same performance in a Web App as a VM/IIS hosted site you need to spend significantly more. I appreciate the Azure VM’s but always imagined that I’d move to Web Apps to leverage the platform and so far it hasn’t made sense. Hope that changes soon. 

Microsoft

Hey @Jakenuts that's a fair observation, the underlying machines are the same, but we built App Service to do more than simple hosting. It is a fully managed environment for building and managing ASP.NET web apps. We built native integrations with Visual Studio and GitHub for live site debugging and automated CI/CD. We created deployment slots so you can ship code changes with no downtime. We have out of the box monitoring designed specifically for ASP.NET apps and built small details like pre-installing URL Rewrite for devs to define custom rules in web.config. This week we’re updating the hardware so your apps can run on the best machines, and lower rates - soon with commitment discounts - to make it more affordable.

Frequent Visitor

Regarding 

With Premium v3, our support for Windows Containers also becomes Generally Available

Would this be next version of Premium Container PC2/PC3/PC4 app service plans? If so, What version of nanoserver container images can be deployed to this environment?

pc2.PNG

 

I had a difficult time deploying windows containers to Azure Container Instances. Specifically, docker images built with nanoserver version 2004, 1909, 1903 fail to deploy on ACI stating UnsupportedWindowsVersion. And the only version supported is nanoserver:1809 which will reach EOL on Nov 10, 2020. Full thread here: https://github.com/dotnet/dotnet-docker/issues/2257#issuecomment-696477226

nanoserver-2004-aci.png

Will Premium V3 environment support deployment of docker images based on nanoserver:2004 ?

Microsoft

HI @prabh62  indeed it does you can deploy containers based on the 20.04 release of Windows Server 2019 and we will also be working upgrade our Windows Container hosts to the latest releases of Windows Server to make it very easy for you to deploy your apps in containers, taking advantages of continued investments in Windows Containers.  You can find out more regarding the base images we cache in App Service and more details on configuration options using this document - https://aka.ms/appsvcwindowscontainersconfiguration

 

Occasional Visitor

Great news, was looking forward to this! :) Two questions:
1) I see some mixed details going round on the web about the new plan sku hardware. Can you confirm it's Dv4? (See mentions about Dv3 also)

2) Is this upgrade also coming to Azure Container Instances? ATM we cannot provision more than 4 vCPU / 16GB per ACI group, would be great if those limits will be extended to 8/32 too!

Frequent Visitor

This is great news. Will the new isolated / ASEv2 which does away with the stamp fee also offer the new Pv3 VM sizes and also on reserved pricing, dev/test etc? (Being able to run apps securely in Azure App Service shouldn’t be an expensive ‘option’ IMO you should just be able to run normal Pv3 machines in your own vnet like normal VMs / scale sets). Thanks.

Frequent Visitor

Hello,

 

I am trying to create an App Service Plan in Azure West US for windows containers and I am still seeing the windows containers preview banner as well as not seeing the Pv3 option to select. Am I missing something? It is Oct 1st so making sure that still is the date.

 

 

JeffBobadilla_0-1601579094169.png

 

This should be live since yesterday, but I'm not seeing any P*v3 offers I can switch to, neither in existing AppService Plans, nor when I create a new one.

Was this released yet?

Occasional Contributor

Ditto on not seeing V3 offers yet... any additional details on this release @JT Rose?

Microsoft

Hi @Jeff @ThomasChristmann and @Derek Gabriel unfortunately the rollout has been delayed to 10/9/2020. Apologies for any inconvenience caused.

Occasional Visitor

This feature is long overdue, I have put my release on hold and counting down to November 1

Microsoft

Further update -  The new Premium V3 SKU and Windows Container GA support is now LIVE and available in the portal, ARM and CLI.  Documentation updates have completed, for example Configure PremiumV3 tier - Azure App Service | Microsoft Docs can answer a number of questions around Premium v3.  cc @Jeff @ThomasChristmann and @Derek Gabriel 

Frequent Visitor

Hi,

May I know the available locations for Premium V3 SKU for Windows Container GA support? I couldn't get the locations list.

was it not released yet?. If so when can we expect it?

 

Thanks.

cc @apwestgarth 

 

>az appservice list-locations --sku P1V3
az appservice list-locations: 'P1V3' is not a valid value for '--sku'. See 'az appservice list-locations --help'.

The most similar choice to 'P1V3' is:
        P1V2

 

Frequent Visitor

Thanks @apwestgarth 

 

Can I get confirmation that using managed identities to connect to an Azure SQL Database works with Windows Containers now? And it works in an App Services setup?

Microsoft

Hi @pragadeesh the feature is indeed available and released as I posted in the comment prior to yours.  Here is the list of locations, I'm not sure why your CLI session did not return the full list, as you will see from the output below this is from AZ CLI:

❯ az appservice list-locations --sku P1v3
[
  {
    "name": "Central US"
  },
  {
    "name": "North Europe"
  },
  {
    "name": "West Europe"
  },
  {
    "name": "Southeast Asia"
  },
  {
    "name": "East Asia"
  },
  {
    "name": "West US"
  },
  {
    "name": "East US"
  },
  {
    "name": "Japan East"
  },
  {
    "name": "East US 2"
  },
  {
    "name": "South Central US"
  },
  {
    "name": "Brazil South"
  },
  {
    "name": "Australia East"
  },
  {
    "name": "Australia Southeast"
  },
  {
    "name": "Canada Central"
  },
  {
    "name": "West Central US"
  },
  {
    "name": "West US 2"
  },
  {
    "name": "UK West"
  },
  {
    "name": "UK South"
  },
  {
    "name": "Korea Central"
  },
  {
    "name": "France Central"
  }
]
Microsoft

@JeffBobadilla yes, Managed Identities are supported for Windows Containers on App Service, meaning you can indeed use a managed identity with other Azure Services, such Azure SQL DB from your Windows Container app in App Service.

Frequent Visitor

Hello @apwestgarth,

 

Thanks for your response.

 

When i tried to create a service plan in WestUS , i bumped into an error (Requested features are not supported in region)

pragadeesh_0-1602005324643.png

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"BadRequest","message":"{\r\n \"Code\": \"BadRequest\",\r\n \"Message\": \"Requested features are not supported in region. Please try another region.\",\r\n \"Target\": null,\r\n \"Details\": [\r\n {\r\n \"Message\": \"Requested features are not supported in region. Please try another region.\"\r\n },\r\n {\r\n \"Code\": \"BadRequest\"\r\n },\r\n {\r\n \"ErrorEntity\": {\r\n \"ExtendedCode\": \"59911\",\r\n \"MessageTemplate\": \"Requested features are not supported in region. Please try another region.\",\r\n \"Parameters\": [],\r\n \"Code\": \"BadRequest\",\r\n \"Message\": \"Requested features are not supported in region. Please try another region.\"\r\n }\r\n }\r\n ],\r\n \"Innererror\": null\r\n}"}]}
Frequent Visitor

Thanks @apwestgarth 

 

But I dont see the managed identities working with windows containers yet as I am still seeing the same errors I have seen in the past where its erroring out trying to connect to the https://database.windows.net/ service point. If I connect with the username and password in the connection string it works as expected. If someone HAS set up managed identities working with windows containers in the App Service please let me know

Microsoft

@pragadeesh can you retry please?  If you hit the same error can you share with me your subscription type and any correlation ID you receive, you should be able to contact me via private message. 

Microsoft

Hi @JeffBobadilla after seeing your response, I went through our documentation (https://docs.microsoft.com/azure/app-service/app-service-web-tutorial-connect-msi) again and setup two new container based instances, both .NET Framework and .NET Core, which connect to Azure SQL Databases using System Assigned Managed Identity, deployed them to two new Pv3 App Service Plans in two regions, and can confirm that both are functioning as expected. I'm sorry you're still experiencing issues with your applications when using Managed Identities. Could you try restarting your application and test once more please? If you are still experiencing an issue, please open a support case and we will be able to look deeper at the issue you are experiencing.

Frequent Visitor

Hmm @apwestgarth you can confirm you are using windows containers for this? I still am not able to get this to work. The article in your link is an older article that is focused on an app running in the app service itself not in a container running in the app service. Also I have yet to find an article that doesn’t say that managed identities only works for Linux containers

Microsoft

Hi @JeffBobadilla yes I can confirm I used both a Windows Server Core container (for the .NET Framework) sample, and a Windows Server Nano container for the (.NET Core) sample.  The article is still valid.  I've put my two samples into repos in my GitHub account:

 

.NET Framework - apwestgarth/DotNetFrameworkSqlDbInWindowsContainer: .NET Framework and Azure SQL DB sample where the authentication method is Managed Identity and the app is deployed in a Windows Container (github.com)
.NET Core - apwestgarth/DotNetCoreSqlDbInWindowsContainer: .NET Core and Azure SQL DB sample where the authentication method is Managed Identity and the app is deployed in a Windows Container (github.com)


I used the article mentioned as the basis to build the application and then I added Docker support and published my app in a container to Azure Container Registry then

  • I created a new Resource Group, App Service Plan (P1v3) and Windows Container web app in East US 2, setting the docker container to be the image I had published;
  • Once the site was created I enabled Managed Identity via the portal
  • I added the Managed Identity to my Azure SQL DB using the steps in the tutorial - Tutorial: Access data with managed identity - Azure App Service | Microsoft Docs
  • I browsed the site and confirmed my application was running correctly.

The app itself is currently running at https://apwmsisampleeastus2.azurewebsites.net

 

Managed Identity is supported across App Service - Windows Code, Windows Containers, Linux Code and Linux Container.  We enabled Managed Identities for Windows Containers in App Service in August 2020, so it is possible we may have missed an update to our docs, I am scanning them all to make sure any errors are rectified.

 

As you are currently still experiencing issues with this functionality, please open a support ticket and we can investigate further and help.

Microsoft

@Embers1  The hosts used for Isolated V2 will be the same type used for Premium V3.  

Frequent Visitor

Thanks so much for the reply @apwestgarth . I am starting to think that this may be an IIS app pool issue that I am facing. When I deploy our application to a Windows IaaS VM and enable managed identity on the VM to authenticate the app with Azure SQL Database, I have to change the app pools to NetworkService to pickup the MI to authenticate. On an IaaS Windows VM this works successfully. But its not working on windows containers, so I am wondering if the app pool identity needs to be set to something other then NetworkService?

Occasional Visitor

Hi @apwestgarth 

 

Will the reserved pricing apply to premium v2 service plan also or it is only for v3 plans?

Microsoft

@rangav185 Reserved instance pricing will only apply to Premium v3 plans.

Visitor

I am having an issue with a .NET Core 3.1 worker service (Microsoft.NET.Sdk.Worker) running in a "windows:1809"-based container (the fat image). Every 21s it outputs the following to the log and the app freezes after 1 min:

 

<time> INFO - Site: <site-name> - [<cont-id>] - Waiting for container to be ready
<time> INFO - Site: <site-name> - [<cont-id>] - Waiting for container to be start. Container Id: <cont-id>

 

Tried re-creating App Service instance - same result. 

I am surprised that the same image works fine on ACI (which still in preview) and fails on App Service (which is now GA).

cc @apwestgarth 

Microsoft

@FeliksM does your container expose a HTTP endpoint?  App Service is a platform for hosting HTTP Workloads and we perform healthchecks on that basis.  If you review this section in our configuration documentation Configure a custom container - Azure App Service | Microsoft Docs you can set the Health Check to report only and then inspect whether or not the container comes up. If you still experience issues please open a support case so we can investigate further.

Microsoft

@JeffBobadilla you do not need to modify IIS Application Pool Identities to have the application run and use Managed Identity.  If you look at the samples I shared, you'll see the Dockerfile includes no additional IIS configuration.  Managed Identity is configured at the app level by the service.

Frequent Visitor

Thanks @apwestgarth . Very strange that it works in an Azure IaaS VM perfectly but fails when its in the windows container. And if I add username and password to the connection string it works like a charm in windows containers. Just not working with MI. Error below is what I get

 

 
One or more errors occurred.
at System.Threading.Tasks.Task`1.GetResultCore(Boolean
waitCompletionNotification)
at System.Data.SqlClient.SqlInternalConnectionTds.<>c__
DisplayClass134_1.<GetFedAuthToken>b__1()
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
 
Parameters: Connection String: [No connection string
specified], Resource: https://database.windows.net/,
8D-401F4BA55C88. Exception Message: Tried the following 4
methods to get an access token, but none of them worked.
Parameters: Connection String: [No connection string
specified], Resource: https://database.windows.net/,
8D-401F4BA55C88. Exception Message: Tried to get token
using Managed Service Identity. Unable to connect to the
Managed Service Identity (MSI) endpoint. Please check
that you are running on an Azure resource that has MSI
setup.
Parameters: Connection String: [No connection string
specified], Resource: https://database.windows.net/,
8D-401F4BA55C88. Exception Message: Tried to get token
using Visual Studio. Access token could not be acquired.
Visual Studio Token provider file not found at "C:\Windows
\system32\config\systemprofile\AppData\Local\.IdentityServ
ice\AzureServiceAuth\tokenprovider.json"
Parameters: Connection String: [No connection string
specified], Resource: https://database.windows.net/,
8D-401F4BA55C88. Exception Message: Tried to get token
using Azure CLI. Access token could not be acquired. 'az'
is not recognized as an internal or external command,
operable program or batch file.
 
Parameters: Connection String: [No connection string
specified], Resource: https://database.windows.net/,
8D-401F4BA55C88. Exception Message: Tried to get token
using Active Directory Integrated Authentication. Access
token could not be acquired. Failed to get user name from
the operating system.Inner Exception : No mapping between
account names and security IDs was done
 
 
Request information:
Request URL: http://10.41.0.7/
Request path: /
User host address: 10.41.0.7
User:
Is authenticated: False
Authentication Type:
Thread account name: NT AUTHORITY\NETWORK SERVICE
 
Thread information:
Thread ID: 12
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace: at System.Web.HttpApplicationFactory.E
nsureAppStartCalledForIntegratedMode(HttpContext context,
HttpApplication app)
at System.Web.HttpApplication.RegisterEventSubscription
sWithIIS(IntPtr appContext, HttpContext context,
MethodInfo[] handlers)
at System.Web.HttpApplication.InitSpecial(HttpApplicati
onState state, MethodInfo[] handlers, IntPtr appContext,
HttpContext context)
at System.Web.HttpApplicationFactory.GetSpecialApplicat
ionInstance(IntPtr appContext, HttpContext context)
at System.Web.Hosting.PipelineRuntime.InitializeApplica
tion(IntPtr appContext)
Visitor

@apwestgarth My container does not expose an HTTP endpoint. It's a continuously running background job but I would still prefer to run it on App Service rather than ACI because App Service is less expensive and is GA now.

I tried setting CONTAINER_AVAILABILITY_CHECK_MODE to "Off" and restarting the service but that had no effect:

FeliksM_0-1602194758733.png

Untitled.png

Visitor

@apwestgarth Tried replacing the base image with "nanoserver-1809" - no issues in App Service. As soon as I go back to the fat image (windows:1809 or windows:2004) it starts looping through those checks every 21s and eventually dies. Are fat images not supported in App Service?

Visitor

@apwestgarth Got to the bottom of this. Despite having CONTAINER_AVAILABILITY_CHECK_MODE set to "Off" and "autoHealEnabled" set to "false" in the ARM template, App Service is still doing some sort of internal checks via port 80 and restarts the container when it doesn't respond. The workaround is to expose and bind port 80:

 

EXPOSE 80
ENV ASPNETCORE_URLS=http://+:80

 

This should not be required for background services without a public endpoint. At the minimum there should be a setting to disable this default behavior. To reiterate, this is not an issue on ACI.

Microsoft

Hi @FeliksM thanks for the feedback.  Principally App Service is a platform for hosting HTTP applications hence why we have such checks in place but ACI does not.  Your use case is great feedback for us though and is something we will look into in more detail.  Our HTTP Endpoint health check is always running and we report if an endpoint is unreachable.  We make theses events visible to help with troubleshooting. 

 

From your latest comment it would appear you were still seeing your container restart, could you either create a support ticket or send me your site name via private message and we can take a look further at our logs please? 

 

Also for reference the Full Windows Server images are also supported, they are much larger however and take much longer to start up as we do not pre-cache those images locally so there are extra layers for us to retrieve.  I validated this by building an IIS based image on top of mcr.microsoft.com/windows:2004 this afternoon.

Visitor

@apwestgarth 

1. Sorry for for the confusion, once I added port 80 config to windows:2004 image the restarts stopped, so I am using that workaround for now. However, App Service does have "WebJobs" option today but it seems to be disabled for containers. Are there any plans to make it available in the future? That would make it easier to host containerized .NET Core worker services.

2. Regarding pre-caching of Full Windows Server images: does that mean that the image is just not pre-cached with a brand new instance of App Service, or that App Service will always fetch the "windows:2004" layer from registry after every stop/start (like ACI does)?

Microsoft

@FeliksM regarding 1. I have looked at how we can enable WebJobs in Windows Containers but so far that would be specifically for using the WebJobs SDK (How to use the WebJobs SDK - Azure App Service | Microsoft Docs ) this investigation work is ongoing.  My personal background is in .NET however so I will also look deeper into the .NET Core Worker Services;


Regarding 2.  When your site is allocated an instance or a number of instances based on your app service plan, that worker has a number of images pre-cached on the worker before we mark it ready to receive workloads.  The full list is here - Configure a custom container - Azure App Service | Microsoft Docs these images are pre-cached in order to make loading of customer's customer containers as efficient as possible, which particular for Windows Containers, can be quite large. 

 

In the case of the Full Windows Image then each time you deploy or scale to a new instance we need to pull and extract any additional base layers, we don't already have cached which make up that base image, in addition to those which contain your content as they don't already exist locally.  However if you have multiple apps per app service plan that all use the same base image then we don't repull for each new app which starts up as the layers already exist, we just pull and extract the layers that are different (primarily app content). 

 

In the event you stop or start your app we don't need to pull and extract again as the layers already exist on the instance on which you are running.  I hope this explains our behaviour, any further questions on this please let me know and I'll be very happy to answer.

 

Out of interest, do you need to have the overhead of the Full Windows Server image, do you need to use a service/feature/api that is not available in the Nano images?  You should still be able to expose a http endpoint on those images too, then you can also benefit for the massive reduction in container size.

Visitor

@apwestgarth Thanks for the detailed explanation, sharing layers across app services hosted on the same plan is a nice feature. Regarding Full Windows Server images: you tested it with an IIS based image and it worked because that image included port configuration whereas in my case it was a plain windows image (with an application layer on top) that kept restarting. The reason I have to use the fat image is because I need to be able to run Chrome headless browser and have it render websites with custom fonts and export them to PDF, which doesn't work on Core or Nano. The other three options are ACI, AKS and VMs: ACI doesn't cache image layers and takes a long time to start, AKS requires a cluster and VMs are harder to manage.

Frequent Visitor

Hi@apwestgarth , Is there any change in the environment that we need to aware of  while using P1V3 for windows container webapp (it works fine on PC2 Plan). and im using node application version 12.18

 

Here is the error im getting

 

16/10/2020 09:12:49.879 ERROR - Site: test - Unable to start container. Error message: Open Compute System failed.
New Contributor

@apwestgarth I attempted to scale up an app service plan to P2V3 using PowerShell, and it scaled to P2 (V1) instead.

 

Set-AzAppServicePlan -ResourceGroupName $usedPlan.ResourceGroup -Name $usedPlan.Name -Tier PremiumV3 -WorkerSize Medium

 

I then tried in the portal and got this error:

 

The pricing tier 'PremiumV3' is not allowed in this resource group. Use this link to learn more: http://go.microsoft.com/fwlink/?LinkId=825764

I see some guidance in the documentation about moving to a new plan, but clicking the Clone button in the portal for a few hundred apps is not really feasible. Are there any other options?

 

Thanks!

 

Occasional Visitor

I have the same problem as @Thomas Mueller. I am trying to add a V3 app service plan (Windows) to an existing resource group. This RG has P3V2 app services currently running and my intention is to upgrade those to V3 plans.

 

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"BadRequest","message":"{
 "Code": "BadRequest",
 "Message": "Requested feature is not available in resource group RGNAME. Please try using a different resource group or create a new one.",
 "Target": null,
 "Details": [
 {
 "Message": "Requested feature is not available in resource group RGNAME. Please try using a different resource group or create a new one."
 },
 {
 "Code": "BadRequest"
 },
 {
 "ErrorEntity": {
 "ExtendedCode": "59324",
 "MessageTemplate": "Requested feature is not available in resource group {0}. Please try using a different resource group or create a new one.",
 "Parameters": [
 "RGNAME"
 ],
 "Code": "BadRequest",
 "Message": "Requested feature is not available in resource group RGNAME. Please try using a different resource group or create a new one."
 }
 }
 ],
 "Innererror": null
}"}]}