Unblocking port 25 limitations in Azure

I run my own mail server on Azure for my domain. After deploying a new VM that will replace my existing server I stumbled upon the inability to run trivial email diagnostic tests like port25's DKIM tester. I found this Microsoft article showing that MS decided to shut down the ability for new deployments to run port 25 and that a support request should be made to unlock port 25 outbound.

The article says that the support request must be for a technical issue, however my subscription does not allow technical support requests unless I buy a paid MSDN subscription.

I run my own domain on a very low budget and mostly for fun than for profit, but I am trying to reduce the number of servers after shutting down my ecommerce hosting business. So I wouldn't like to pay for a subscription that is worth more than the two servers I currently run.

How can I request port 25 unlock and go through Microsoft's screening without the ability to issue technical requests?

The answer is in the article you linked: use an authenticated and encrypted mail submission agent.

However, this will limit your ability to connect to MTAs on port 25. Presumably, this is by design, as there are less attentive Azure customers contributing to the junk mail problem.

Recommended Method of Sending E-mail

Microsoft recommends that Azure customers employ authenticated SMTP relay services (typically connected via TCP port 587 or 443, but often support other ports too) to send e-mail from Azure VMs or from Azure App Services. These services specialize in sender reputation to minimize the possibility 3rd party e-mail providers will reject the message. Such SMTP relay services include but are not limited to Exchange Online Protection and SendGrid.

Use of these e-mail delivery services is in no way restricted in Azure regardless of subscription type.