...
BloxOne DDI does not support Azure DNS tags.
BloxOne DDI does not provide support for the creation of Multiple Third Party DNS providers for the same Azure Subscription ID.
BloxOne DDI does not support non-simple routing policy records.
BloxOne DDI only supports static credentials for Azure right now.
Azure supports multiple values for a resource record set. After data synchronization, BloxOne DDI creates multiple records (one for each value that is specified in Azure).
BloxOne DDI does not allow updates or deletions to NS records synchronized with Azure since it is a system record.
SOA records synchronized from BloxOne DDI to Azure may take several sync intervals to update. The SOA details that support synchronization are refresh, retry, expire, negative TTL, MNAMERNAME, and default TTL.
The RNAME MNAME field is not synchronized between Azure and BloxOne DDI, nor is the Serial Number.
Following are the Azure supported alias records and corresponding conversions in B1DDI:
Azure Front Door Resources:
Converted to B1DDI CNAME Records
properties.cName field stored as CNAME in B1DDI
Azure Traffic Manager:
Converted to B1DDI CNAME Records
properties.fqdn field stored as CNAME in B1DDI
Azure CDN:
Converted to B1DDI CNAME Records
properties.hostName field stored as CNAME in B1DDI
Public IP:
Converted to IPv4/IPv6 Record as per the target source
properties.ipAddress field stored as address in B1DDI
Static Web App:
Converted to B1DDI CNAME Records
properties.defaultHostname field stored as CNAME in B1