We have a split estate between on-premise and cloud. Our DNS is hosted on Azure DNS.
We have a program which runs on our on-premise hosted servers and updates the Azure DNS service via the Azure REST API with the server's public IP address (these servers are generally located on residential ADSL connections). Basically, a home-grown replacement for noip.com.
The program does a straight update each time, even if the IP address is unchanged. The API does of course provide read access, so we could modify our program to check the current IP first, but (obviously) the number of API calls would actually go up slightly with this approach.
The volume of requests will never be large (say, max of 300 servers with the program running every 10 minutes) but it would be higher, in proportion to the size of our account, than a typical management application might create.
I have been unable to find any information about API rate limits or usage guidelines.
What I want to avoid is an unexpected loss of service, so I would be grateful for any guidance regarding whether this would be an approved use of the API and any information regarding API rate limits.