Microsoft Dynamics 365 Blog

More Info:  Impacted users may have received an error message stating, “VOICE EXPIRED.”

Final Status: After further review of the error logs, we identified a configuration error that occurred after a recent deployment. We updated the affected infrastructure, restoring the ability to access AX 2012 projects.

Update 3: We are continuing to collect logs and review telemetry to determine the cause of this issue.

Update 2: Our refresh of front-end servers has completed successfully, and we have verified that there are no certification issues. We are continuing our investigation to determine the cause of this issue.

Update 1: After investigation, it was discovered that calls to the server may be failing for impacted users. We are currently in the process of restarting front-end servers and monitoring service health. Concurrently, we are reviewing certificates to determine if there is any issue with authentication.

Incident Start Time: Sunday, April 15, 2018, 9:59 AM UTC

Incident End Time: Monday, April 16, 2018, 13:55 PM UTC

Preliminary Root Cause: After a recent deployment, we identified a misconfiguration on the infrastructure responsible for accessing AX 2012 projects.

Next Steps: We’re reviewing our deployment and provisioning procedures to help prevent similar problems in the future.

This is the final update on the incident.

We're always looking for feedback and would like to hear from you. Please head to the Dynamics 365 Community to start a discussion, ask questions, and tell us what you think!