1. Azure Service Update Management Scenarios
Click the play button to begin

2. Good luck! Get Started How to Proceed
In this section, there are two scenarios which address the following topics.
Security Updates
Release Schedules
You can proceed through the scenarios in order by clicking the Get Started button in the lower right corner of this page.
For each scenario, you will be provided with a short introduction and then asked a question. The flow of the scenario will vary based on your answers
In this section, there are two scenarios which address the following topics.
Security Updates
Release Schedules
You can proceed through the scenarios in order by clicking the Get Started button in the lower right corner of this page.
For each scenario, you will be provided with a short introduction and then asked a question. The flow of the scenario will vary based on your answers
Good luck!
Get Started

3. Good luck! Get Started How to Proceed
In this section, there are two scenarios which address the following topics.
Security Updates
Release Schedules
You can proceed through the scenarios in order by clicking the Get Started button in the lower right corner of this page.
For each scenario, you will be provided with a short introduction and then asked a question. The flow of the scenario will vary based on your answers
Good luck!
Get Started

4. Purpose: Benefits: Next Page Purpose & Benefits
To demonstrate how to handle Azure service updates and release schedules
To be able to manage Azure service updates more effectively and efficiently
Next Page

5. As the TAM/ADM, what do you do?
Scenario 1-1
Your customer lets you know that they think a security update was applied to a host OS and they think it caused a reboot of their VMs which impacted an application that was running. The customer has already opened a SR with Support for troubleshooting.
Customer
Did you make a recent update? I think it caused an issue for us.
TAM
Hi, I’m sorry to hear that. Could you please be more specific?
Customer
Well, something caused reboot of our VM’s and that impacted an application that was running. Why weren’t we notified about this update?
As the TAM/ADM, what do you do?
(Click one of the following options)
You search the last Azure SUM newsletter for details and you check Iridias Maintenance events and Message Center to see if the customer should have seen the events in their Service Health Dashboard.
You review the Azure FAQ to see if this issue is highlighted.

6. Scenario 1-1 correct
Correct!
You search the Azure FAQ located here which states that you can use ACIS to look up maintenance impact to a specific subscription and you can also see who is set up as admins and co-admins with valid addresses. These contacts will receive notifications in some instances.
You also note that TAMs are NOT copied on the s to customers today.
You also bookmark the FAQ for future reference.
Next scenario

7. Sorry, this is incorrect.
Scenario 1-1 wrong
Sorry, this is incorrect.
After spending one hour reading and searching the Azure newsletter, you determine that this information is not contained in the newsletter.
After spending 30 minutes searching the SHD, you realize that you don't see any Azure maintenance events. Azure maintenance events are not shown in the O365 SHD.
The correct answer is to review the Azure FAQ located here which states that you can use ACIS to look up maintenance impact to a specific subscription and you can also see who is set up as admins and co-admins with valid addresses. These contacts will receive notifications in some instances.
Bookmark the FAQ for future reference.
Try again

8. Scenario 2-1
You also learn from reading the FAQ that there is a tool that you can review to determine Azure release schedules ahead of time. What is this tool?
Which tool is it?
(Click one of the following options)
SHD
Azure Portal
Calendar schedule of outgoing/scheduled s

9. Sorry, this is incorrect.
Scenario 2-1 wrong
Sorry, this is incorrect.
Azure maintenance events are not shown in the O365 SHD.
The calendar schedule of outgoing/scheduled s to be sent to customers regarding GA capabilities, support notices, etc. is the best choice to determine Azure release schedules ahead of time.
Try again

10. Sorry, this is incorrect.
Scenario 2-1 wrong
Sorry, this is incorrect.
Azure portal may get you the information but not in all cases. See blog here.
The calendar schedule of outgoing/scheduled s to be sent to customers regarding GA capabilities, support notices, etc. is the best choice to determine Azure release schedules ahead of time.
Try again

11. Scenario 2-1 correct
Correct!
The calendar schedule of outgoing/scheduled s to be sent to customers regarding GA capabilities, support notices, etc. is the best choice to determine Azure release schedules ahead of time.
Next page

12. Key Points Take Action Summary
Use the Calendar Schedule and ACIS to internally view the customer communication schedules.
Microsoft will provide notification 12 months before retiring a SDK.
Take Action
For future reference, bookmark the FAQ
Check the Azure Blog regularly for updates