Transition from VNET integration to public access or Private Link using the Azure CLI
This post provides two bash scripts that use the Azure CLI to transition an Azure Database for MySQL flexible server from VNET Integrated to Public Access or a Private Link. You can run these bash scripts either locally or by using the Azure Cloud Shell.Compliance Recording Bot invite coming from unknown subnet
Hello, As of this morning, all my compliance recording bots fail to record my personal account. Invites are filtered by FW, with this IP range configuration, as stated https://learn.microsoft.com/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide 52.112.0.0/14 52.122.0.0/15 When disabling firewall rules, invites are coming through. And are originated from 9.163.189.144 or 20.82.235.109, which don't match the above IP range .... Only my user sounds affected by this recent change in my tenant. As we have many customers using our compliance recording bot, we have opened all the ports in the firewall, which is not a good practice. Could I have some feedback about this issue ? Is Microsoft changing its IP ranges ? Thanks for your answer
