ASP.NET Core 3.1 WebApp - is the warning about static files still valid?

[wpqs]

I seem to have successfully installed the Lets Encrypt Site Extension for my ASP.NET Core webapp even though I ignored the warning message:

WARNING Before you proceed ensure that you site can serve static files from a 
http:///.well-known/acme-challenge/ folder that is create by the extension, if you 
application cannot serve static files from that folder the site extension will not be 
able to do its job (the extension will create the folder). Please note Lets Encrypt 
servers will access the path over http. If you application is .NET ASP application, 
the extension will place a web.config in the folder, so then you don't have to do 
anything, but if you application is a node.js, java or .NET core application you have 
to ensure that static files can be served from the folder.

Creating a Visual Studio project from a template for an ASP.NET Core 3.1 Web App creates a site with static files enabled, but only from the root directory (wwwroot) see - Microsoft docs - static files for aspnetcore-3-1. Furthermore, looking at the Kudu debug console the required folder seems to have been created off wwwroot:

 D:\home\site\wwwroot\.well-known\acme-challenge 

Question: is the warning about static files still valid, or do I need to take any further configuration steps for my ASP.NET Core 3.1 Web App?