Blazor webassembly with Authentication rack up unusal out bandwidth charges
I have 2 blazor webassembly apps deployed to Azure App Services, one with Identity setup and one without Identity setup. The blazor webassembly with Identity setup is racking up unusual out bandwidth charges. In just one day it used up my entire monthly budget. I don't understand why the blazor webassembly with Identity setup is using so much "out" bandwidth. The blazor webassembly without the Identity setup is barely using any bandwidth. The problem can be replicated my creating a new Blazor webassembly project with Identity from Visual Studio 2019. To bypass the identity server key issue, I set the key to "development". I then publish the <myapp>.Server project to a .NET 5 (Preview) framework App Service that I setup. As soon as I publish the app, the unusually out bandwidth can be seen. Does anyone know what is going on? Thanks.