What's New in MOS
- Create/Update User Endpoint (Integration API)
What's New
- Operators can now manage user access more flexibly via the existing Create/Update User endpoint, including Business Unit access and global access flags—without breaking existing integrations.
Why This Matters
- This unlocks better self-service and cleaner integrations, while keeping full backward compatibility for current clients.
What's Improved
- Clearer access rules (all business units / specific business units / departments) and more reliable user matching when updating users.
- Retrieve All Statuses in Get BU Integration Endpoint
What's New
- The Business Units endpoint now supports filtering by all valid Business Unit lifecycle statuses (not just Active/Inactive).
Why This Matters
- Integration clients can fully sync the Business Unit lifecycle, avoiding missing or invisible locations in external systems.
What's Improved
- More complete results when no filter is provided, plus clearer validation messaging when a status is invalid.
- Remove Capability List from Get BU Integration Endpoint
What's New
- The Get Business Unit details response no longer returns the unnecessary application Capabilities field.
Why This Matters
- Simpler, cleaner payloads reduce confusion and keep the API focused on business-relevant data.
What's Improved
- Less noise in responses while keeping all required Business Unit information unchanged.
- Remove userFeedId from getBusinessUnits Response (Integration API)
What's New
- The userFeedId field (previously returned as null) has been removed from the business-units response payload.
Why This Matters
- Reduces confusion for consumers and keeps responses aligned with what is actually supported.
What's Improved
- Cleaner contracts and easier downstream mapping for integration clients.
- LATAM Support for Document Management
What's New
- Complete the remaining work required to ensure Document Management is fully operational and validated for LATAM deployments, including document uploads, platform configuration, and supporting services.
Why This Matters
- As MOS expands into LATAM, users must have access to the same document management capabilities available in other regions.
What's Improved
- The LATAM environment was reviewed and validated to confirm that document upload processes, configurations, integrations, and related services are correctly deployed and functioning as expected.
- LATAM Support – Verify Azure Function App is Working Correctly in pro-mxc Environment
What's New
- We completed a health check of the mapalos-function-app-prod Azure Function App in pro-mxc, focusing on its two Service Bus-triggered processes (OnBundlesUpdated and OnLogMessageAdded).
Why This Matters
- These background processes keep key MOS operations running smoothly. If messages stop being processed or pile up, it can lead to delays, missing updates, and operational issues.
What's Improved
- Confirmed successful triggering in Application Insights, balanced Service Bus message flow, no active queue backlog, dead-letter queue verification, and no unexplained errors in the last seven days.

