Import Key Vault Certificate

[SteveSandersonMS]

See dotnet/aspnetcore#29891

[lohithgn]

@marcelWCH
In Step 10 of the workshop, the instruction to add a certificate is not for your Database. At the end of the section "Publishing to a new App Service", you can refer to the following statement:
If we publish the app at this point, it will return a server error and fail to start. This is because we first need to configure a signing key for Identity Server. During development, we used a development key (see BlazingPizza.Server/appsettings.Development.json), but in production we need to configure an actual certificate for issuing tokens. We'll do that using Azure Key Vault.
As you can see, The application makes use of Identity Server as an Identity Provider for your application. While developing locally it uses local development certificate to encrypt the identity token. But when you deploy to your app service - you need a certificate uploaded to your app service for the token to be encrypted.

With respect to you not able to add a certificate to your app service: The portal is already giving you a warning that "SSL bindings can be used in Basic plans and higher". Looks like you have your pricing tier set to F1 (Free) or D1 (Shared) tier. You need to be in minimum BASIC tier or above BASIC tier to add a TLS/SSL certificate.

Hope this clarifies your question.