mage-os / mageos-async-events-azure

mage-os/mageos-async-events-azure

magento2-module Compatibility: 2.4.7-2.4.9 Code Quality: Fail Tests: N/A Security: Pass MIT

MageOS Async Events Azure

Azure event sinks for mageos-async-events

Installation

composer require mage-os/mageos-async-events-azure

Authentication

Microsoft Entra is used to authenticate with Azure services. An Azure Service
Principal with the EventGrid Data Sender role is required so that the notifier
can relay events into Azure Event Grid.

Configure OAuth parameters in the Magento admin panel.

Under Stores -> Services -> Async Events Azure set the Tenant ID,
Client ID and the Client Secret.

Best Practices

  • Create a resource group for Magento and assign RBAC permissions to the service
    principal at the resource group level.
  • Create a separate Event Grid topic for each Magento website.
  • For further filtering such as based on magento stores or event types, use
    Azure Event Grid's advanced filtering capabilities.

[image: Azure Best Practice]

Azure event sinks

Azure Event Grid

This module provides an event sink for Azure Event Grid. This allows you to relay
events into Azure Event Grid, enabling you to integrate with other Azure
services or third-party applications that support Event Grid.

The Event Grid topic must use the CloudEvents schema. Events are sent in the
structured content mode of CloudEvents.

Create an Event Grid Subscription

The following is an example to create an Event Grid subscription for the example.event

curl --location --request POST 'https://test.mageos.dev/rest/V1/async_event' \
--header 'Authorization: Bearer TOKEN' \
--header 'Content-Type: application/json' \
--data-raw '{
    "asyncEvent": {
        "event_name": "example.event",
        "recipient_url": "Event Grid Topic Endpoint",
        "verification_token": "secret",
        "metadata": "eventgrid"
    }
}'

Contributing

This is a repository for distribution only.
Contributions are welcome on the development
repository mageos-async-events-sinks

No changelog yet

The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.

Versions
Version Stability QA Status Compatibility Released
4.0.3 stable Fail Magento 2.4.7-2.4.9 Details 2026-02-09 07:38:39

Requires 2

Package Constraint
php >=8.1
mage-os/mageos-async-events ^4.0

Compatibility

Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.

Compatibility matrix (Magento × PHP)
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 Pass Pass
2.4.8 Pass Pass
2.4.9 Pass Pass

Code Quality

Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge — a phpcs finding can't make a module incompatible.

Static analysis

Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.

Static analysis results
Tool Status Findings Summary
PHPCS Fail 4 1 error, 3 warnings (ruleset: Magento2) — 2 auto-fixable with phpcbf
PHPMD Warning 1 1 rule violation (MissingImport:1)
Cpd Pass 0
Composer validate Pass 0

PHPStan

Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases. Cell → details modal.

PHPStan results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 25 25
2.4.8 25 25
2.4.9 25 25

Tests

Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.

Unit tests

Unit tests results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 N/A N/A
2.4.8 N/A N/A
2.4.9 N/A N/A

Integration tests

Integration tests results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 N/A N/A
2.4.8 N/A N/A
2.4.9 N/A N/A

Security

Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.

Security results
Tool Status Findings Summary
Composer audit Pass 0
Malware scan Pass 0
License
MIT

More from mage-os

View vendor
Make it pay

Turn an existing module into recurring revenue.

If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.