Microsoft Operations Support Procedures

An Exigent Circumstance in Microsoft operations refers to emergency situations requiring immediate action from law enforcement or emergency response agencies. Option A correctly identifies this as a phone call or email requesting Microsoft's assistance. Options B, C, and D describe different scenarios but don't match the standard definition of exigent circumstance.

Internal Notifications in Microsoft's operational context are communications sent to internal Microsoft employees. Option B correctly identifies this as emails sent to customers who work for Microsoft (internal customers). Options A, C, and D describe different communication scenarios that don't match the definition of internal notification.

EMT is a standard acronym in Microsoft's operations infrastructure that stands for Emergency Management Team. Option B is correct. Options A, C, and D are incorrect expansions that don't represent the actual meaning of EMT in this context.

Sev0 (Severity 0) and Sev1 (Severity 1) are the highest priority issues that require immediate escalation to prevent significant service impact. Option A is correct - these must be escalated as soon as possible, without waiting for specific time intervals mentioned in options B, C, and D.

Monitoring issues in Microsoft operations require a structured investigation process rather than being handled as normal issues or ignored. Option B is correct - a monitoring investigation ticket must be created to properly track and diagnose the monitoring problem. Options A, C, and D represent incorrect approaches to handling monitoring-specific issues.

A hotswappable DCS (Data Center Services) device is designed to be replaced without requiring system downtime. Option C is correct - hotswap capability means the device doesn't need downtime for replacement. Options A, B, and D describe scenarios that don't align with the hotswappable concept.

NON-US DCS (Data Center Services) request tickets with low and medium priority require two-way escalation to ensure proper handling across regions. Option B is correct - these tickets are 2-way escalated. Options A, C, and D describe incorrect escalation procedures (one-way, reassignment, or 3-way).

When DCS requires additional information to complete a request, the most efficient approach is to directly contact the property source. This direct communication eliminates unnecessary escalation layers and provides the fastest resolution. Escalation paths like T0ES or AOD are meant for different scenarios and would introduce delays.

DEN is classified as a Premium domain within the organizational domain structure. Premium domains typically have enhanced features, higher service levels, or special security requirements compared to standard domains. The classification affects access protocols and support procedures.

Stuck alarms on the console require following documented wiki procedures to ensure proper clearance and avoid service disruption. Wiki procedures provide standardized steps that account for dependencies and potential impacts. Recycling services or escalating without following proper protocol can cause wider issues.

Runner issues are specifically tracked and monitored through the TMF system. TMF provides the centralized view of runner health, performance metrics, and issues. OLA Watcher, iAdmin, and Alarm console serve different monitoring purposes and are not the primary tools for Runner issues.

Request Ticket Templates are stored in both UTS and IMC systems to provide redundancy and accessibility. UTS handles one aspect of template management while IMC covers another, ensuring templates are available regardless of which system the request originates from. Octane XML is not the correct location for these templates.

High-priority request tickets require special handling based on CEN guidelines, which may include emailing relevant parties, two-way escalation, or both depending on the situation. The CEN framework determines the appropriate communication path. Simply one-way escalating or normally handling would not meet the requirements for high-priority items.

Domain access requests are specifically handled through the MSNAccount system, which manages the authorization and provisioning workflow. MSNAlert, MSN Services, and generic MSN are not the correct channels for domain access requests. MSNAccount provides the proper access control and audit trail.

The 'soccust' alias encompasses all teams and aliases supported by MOC, providing comprehensive distribution coverage. It is not limited to just directors, property groups, or TCS analysts/engineers. This broad scope ensures MOC-supported communications reach all relevant stakeholders efficiently.

Critical calls require comprehensive participation from all key roles: AOD (Analyst on Duty), OPM (Operations Manager), SE (Support Engineer), and Shift Lead. Each role brings unique perspective and authority needed for decision-making. Excluding any role would miss critical input and could delay resolution.

Contact information is centralized in iAdmin, which serves as the primary directory for organizational contacts. UTS, IMC, and generic Email are not the designated contact information repositories. iAdmin provides the most up-to-date and comprehensive contact details.

When the primary notification tool fails, the .oft backup template must be used to ensure notifications are still sent. Skipping notifications or waiting for tool recovery are not acceptable options as they delay critical communication. Constructing manual notifications is unnecessary when a backup template exists. The .oft template maintains consistency in notification format.

SHM stands for Service Health Monitor, which tracks the health and performance of services. It is not related to Server Heat, Server Host Management, or being a Manager. SHM provides monitoring alerts and metrics specifically for service availability and performance issues.

PII handling follows documented security policies that establish consistent standards across the organization. A security policy provides the governance framework, whereas teams and individuals implement those controls.