Microsoft Azure Service Issue Summary Tracking Id: QO17-KRO

Title: Virtual Machines - East US

Tracking Id: QO17-KRO
Event type: Service Issue
Region(s): East US
Services(s): Virtual Machines
Start time: 16:42 UTC, 10/29/2017
Resolve time: Ongoing as of 05:53 UTC, 10/31/2017
Last update time: 19:49 UTC, 10/30/2017
Last update: Starting at 16:42 UTC on 29 Oct 2017 you have been identified as
a customer using Virtual Machines in East US who may receive
error notifications when provisioning B-Series, Dv3-Series, Ev3-
Series, DSv3-Series, and ESv3-Series Virtual Machines in this
region. Starting Virtual Machines - with the same SKUs - which are
currently in a "Stopped (Deallocated)” state may also return
errors. As a workaround, customers can attempt to deploy these
Virtual Machine SKUs in the East US 2 region. Alternatively,
customers should be able to deploy Dv2 and DSv2 series Virtual
Machines in the East US region normally. Engineers have
identified a possible underlying cause, and are working to
determine mitigation options. The next update will be provided
upon mitigation, or as events warrant.
Potentially impacted subscriptions: e2186114-ebc1-4579-87b0-d455b33cd6cf (WabtecONE Cloud)

-1-
Microsoft Azure Service Issue Summary Tracking Id: QO17-KRO
Update history: 19:49 UTC, 10/30/2017
Starting at 16:42 UTC on 29 Oct 2017 you have been identified as
a customer using Virtual Machines in East US who may receive
error notifications when provisioning B-Series, Dv3-Series, Ev3-
Series, DSv3-Series, and ESv3-Series Virtual Machines in this
region. Starting Virtual Machines - with the same SKUs - which are
currently in a "Stopped (Deallocated)” state may also return
errors. As a workaround, customers can attempt to deploy these
Virtual Machine SKUs in the East US 2 region. Alternatively,
customers should be able to deploy Dv2 and DSv2 series Virtual
Machines in the East US region normally. Engineers have
identified a possible underlying cause, and are working to
determine mitigation options. The next update will be provided
upon mitigation, or as events warrant.

15:15 UTC, 10/30/2017

Starting at 16:42 UTC on 29 Oct 2017 you have been identified as
a customer using Virtual Machines in East US who may receive
error notifications when provisioning B-Series, Dv3-Series, Ev3-
Series, DSv3-Series, and ESv3-Series Virtual Machines in this
region. Starting Virtual Machines - with the same SKUs - which are
currently in a "Stopped (Deallocated)” state may also return
errors. As a workaround, customers can attempt to deploy these
Virtual Machine SKUs in the East US 2 region. Engineers have
identified a possible underlying cause, and are working to
determine mitigation options. The next update will be provided
upon mitigation, or as events warrant.

10:10 UTC, 10/30/2017

Starting at 16:42 UTC on 29 Oct 2017 you have been identified as
a customer using Virtual Machines in East US who may receive
failure notifications when performing "Create"
Service Management operations, or when restarting resources
hosted in this region. Engineers have identified a possible
underlying cause, and are working to determine mitigation
options. The next update will be provided in 6 hours, or as events
warrant.

08:13 UTC, 10/30/2017

Starting at 16:42 UTC on 29 Oct 2017 you have been identified as
a customer using Virtual Machines in East US who may receive
failure notifications when performing the create service
management operation or restarting resources hosted in this
region. Engineers are aware of this issue and are actively
investigating. The next update will be provided in 2 hours, or as
events warrant.
-2-

08:10 UTC, 10/30/2017