Managed Availability works by implementing Probes, Monitors
and Responders:
 The Probe is the component that performs the simple test. It
doesn’t care whether the test passes or fails. It simply
performs the test.
 The Monitor consumes the results of the Probe, and uses
that to determine the Health state of the item being
monitored.
 Depending on the Health state, one or more graduated
Responder actions may be invoked. All of this information is
logged in the Crimson event channel under Active
Monitoring, or Managed Availability.











•
•
•
•
•
•
•
•
•
•
•
•
•
•
•


•
•
•
•
•
•
•
•
•
•
•
1. Get-HealthReport and Get-ServerHealth
(Current snapshot)
2. Review Current Managed Availability Logging
3. Investigate Managed Availability Recovery
Actions Results
4. Correlate Recovery Action Results to the
appropriate Probe
5. Review the Probe failures to determine next
steps
1. Review the HealthReport and
Server Health (Current
snapshot)
2. Review Current Managed
Availability Logging
3. Investigate Managed
Availability Recovery Actions
Results
4. Correlate Recovery Action
Results to the appropriate
Probe
5. Review the Probe failures to
determine next steps
http://aka.ms/m.a.t.s
Pre-Release Programs
Be first in line!
Exchange & SharePoint On-Premises Programs
Customers get:
Early access to new features
Opportunity to shape features
Close relationship with the product teams
Opportunity to provide feedback
Technical conference calls with members of the
product teams
Opportunity to review and comment on
documentation
Get selected to be in a program:
Sign-up at Ignite at the Preview Program desk
OR
Fill out a nomination: http://aka.ms/joinoffice
Questions:
Visit the Preview Program desk in the Expo Hall
Contact us at: [email protected]
aka.ms/devops
aka.ms/iac_tlp
RSVP
here
aka.ms/devopsmva
#TalkDevOps
http://myignite.microsoft.com