The template error page should recommend checking the server logs.

[Tratcher]

AzureAD/microsoft-identity-web#1213

When there's an exception in production the default template experience shows the following error page:

aspnetcore/src/ProjectTemplates/Web.Spa.ProjectTemplates/content/React-CSharp/Pages/Error.cshtml

Lines 7 to 26 in af96aba

	<h1 class="text-danger">Error.</h1>
	<h2 class="text-danger">An error occurred while processing your request.</h2>
	@if (Model.ShowRequestId)
	{
	<p>
	<strong>Request ID:</strong> <code>@Model.RequestId</code>
	</p>
	}
	<h3>Development Mode</h3>
	<p>
	Swapping to the <strong>Development</strong> environment displays detailed information about the error that occurred.
	</p>
	<p>
	<strong>The Development environment shouldn't be enabled for deployed applications.</strong>
	It can result in displaying sensitive information from exceptions to end users.
	For local debugging, enable the <strong>Development</strong> environment by setting the <strong>ASPNETCORE_ENVIRONMENT</strong> environment variable to <strong>Development</strong>
	and restarting the app.
	</p>

This page recommends enabling Development mode to see details, but not to do that in production.

The page should first recommend checking the server logs for the error details and link to instructions on configuring logging.

[mkArtakMSFT]

@Tratcher do you want to send the PR?

Thanks for contacting us.

We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.