Improved AWS EC2 Resource Name display

Improved AWS EC2 Resource Name display
February 27, 2025

Estimated date for change: March 2025
We’re enhancing how resource names are shown for AWS EC2 instances in our platform. If an EC2 instance has a “name” tag defined, the Resource Name field will now display the value of that tag. If no “name” tag is present, the Resource Name field will continue to show the instance ID as before. The Resource ID will still be available in the Resource ID field for reference.

Using the EC2 “name” tag lets you easily identify your resources with custom, meaningful names instead of IDs. This makes it quicker to locate and manage specific instances, reducing the time and effort spent searching or cross-referencing instance details.

On-demand malware scanning in Microsoft Defender for Storage
February 27, 2025
On-demand malware scanning in Microsoft Defender for Storage, now in GA, enables scanning of existing blobs in Azure Storage accounts whenever needed. Scans can be initiated from the Azure portal UI or via the REST API, supporting automation through Logic Apps, Automation playbooks, and PowerShell scripts. This feature uses Microsoft Defender Antivirus with the latest malware definitions for every scan and provides upfront cost estimation in the Azure portal before scanning.

Use cases:

• Incident response: Scan specific storage accounts after detecting suspicious activity.
• Security baseline: Scan all stored data when first enabling Defender for Storage.
• Compliance: Set automation to schedule scans that help meet regulatory and data protection standards.
  For more information, see On-demand malware scanning.

Defender for Storage malware scanning for blobs up to 50 GB
February 27, 2025

Defender for Storage malware scanning now supports blobs up to 50GB in size (previously limited to 2GB).

Please note that for storage accounts where large blobs are uploaded, the increased blob size limit will result in higher monthly charges.

To avoid unexpected high charges, you may want to set an appropriate cap on the total GB scanned per month. For more information, see Cost control for on-upload malware scanning.