Loading...
Loading...
- mdmsyncmgr fails to retrieve NonCompliantDevice details from Intune - APM logs show authentication errors during device detail updates: “Authentication error for get all non-compliant devices request” - Azure Blob Storage responds with HTTP 403 AuthenticationFailed and message: “Signature fields not well formed” - Packet capture shows SAS signature truncated in redirected request - Issue correlates with the presence of two newly added HTTP headers in Intune redirect response
- NonCompliantDevice retrieval fails completely - Device compliance data cannot be synchronized from Intune - Affects visibility and enforcement of compliance policies
- BIG-IP APM configured with mdmsyncmgr and Microsoft Intune integration - Intune returns an HTTP 303 redirect to Azure Blob Storage with an SAS token - Redirect response includes additional HTTP headers (recent change on Intune side) - Resulting HTTP request size exceeds internal handling limit (~1515 bytes observed) - mdmsyncmgr follows the redirect (HTTP scheme) and truncates the request payload (~15 bytes lost).
None
None
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.