...
Remote Desktop Services can be configured to deliver a HTML5 web client of the published applications. This may be desired over the RemoteApp solution.
hosts file
In order for the RDS VM to be able resolve DNS requests to itself using the FQDN, an entry should be added to the hosts file.
Edit the C:\Windows\System32\drivers\etc\hosts file to point the FQDN to 127.0.0.1
This will allow you to, say open a web browser and navigate to https://jiwards.jiwa.com.au and it be able to reach the locally running IIS instance for the web client.
This is not an essential configuration, but is sometimes useful.
Where this may be essential is if you are running the API self hosted service on the VM, have configured for HTTPS and wish to use the custom domain FQDN.
Secure the Remote Desktop Server
...
Now that the Remote Desktop Gateway is configured, we only need to leave port 443 open (HTTPS) and port 80 (HTTP). The RemoteApp, Webclient and HTML5 client all require port 443 (HTTPS), and we also need port 80 open for the regular 3 monthly certificate renewal automatically performed by the win-acme client.
The rule in the Azure firewall for port 3389 to be open should be removed.
App Registration for Email through Office 365 (Microsoft Graph API)
...
Azure SQL servers never need to be backed up, as this is already done for you. You may wish, however to opt-in to geo-redundant storage to replicate a copy of the database(s) to another other Azure datacenter(s) in case of natural disaster or other catastrophe.
By default, the Azure SQL servers are replicated in real-time to 3 different failover nodes in different fault zones in the datacenter, and should one of those machines, or one of the components, fail - then the requests are automatically redirected to one of the failover machines and a new machine provisioned automatically to replace the failed machine. If you choose geo-redundant storage, then the same applies to the datacenters replicated to.
You may wish to extend the data retention period for the point-in-time backups beyond the standard 7 to 35 days. Up to 10 years of data retention of point-in-time restore is available.
You can also manually export the database to a storage blob or even local file system if desired.
MS Azure Calculator
If you haven’t already, you can use the Azure pricing calculator to see the pricing options - https://azure.microsoft.com/en-au/pricing/calculator
...