Microsoft Technology Licensing, LLC

Charlie Ricafort Chung

Mayank Mehta

Jaya Matthew

Mayerber Carvalho Neto

Charles R Salada

Wilbert De Graaf

Tariq Sharif

Jeremy De Souza

Jon Barry Avner

Mihai R Jalobeanu

Srinivasa Reddy Manda

Ankit Gupta

Rajmohan Rajagopalan

Dipak Sarjerao Pawar

William Hart Holmes

Wilson Li

Victoria Elizabeth Milton

Julia Nancy Foran

Montine Andrea Rummel

Hemant Sharma

Alexander MacLeod

Mirela Dal Col Silva Correa

Prasanna Kumar Padmanabhan

Shubhankar Sanyal

Tor-Helge Persett

Chiquita Kerur

Mohit Mehtani

Sindhura Gangireddy

Alexis Jacqueline Benter

Victoria Carolina Rodriguez

Nirav Jasapara

Oleksandr Bublichenko

Chanchai Ravindra Kariwala

Sean Usher

Roma Ajit Shah

Haebin Seo

Event workflow management in computing systems are disclosed herein. In one example, a process includes receiving a data package defining an event containing data representing a category corresponding to a type of activity of the event and having a workflow property. The process can then include creating or modifying a backend workflow of the event corresponding to the workflow property of the category and monitoring for the one or more status conditions of the event included in the backend workflow. When the monitoring indicates that the one or more status conditions of the event are satisfied, the one or more actions in the sequence of the backend workflow are executed in relation to the event.

Customizable event management in computing systems

A computing device includes a processor and associated memory. The processor is configured to execute a personal information management service stored in memory to send a first calendar entry for display on a calendar interface for a user. The first calendar entry is for a first account of the user of a first domain. The processor sends a second calendar entry for display on the calendar interface. The second calendar entry is for a calendar of a second account of the user of a second domain. The processor receives a request for an availability of the user from a requesting user having a third account of the first domain. In response to the request, the processor sends to the requesting user the first calendar entry including first calendar entry details, and the second calendar entry without second calendar entry details.

User availability in personal information management service

In non-limiting examples of the present disclosure, systems, methods and devices for providing cross-domain access to calendar availability are presented. A request to schedule an event may be received. The request may comprise an identity of an organizer user account, the organizer user account associated with a first domain, and an identity of an invitee user account, the invitee user account associated with a second domain. An importance level of the organizer user account to the invitee user account may be determined. A determination may be made as to whether the organizer user account has access to events in an electronic calendar associated with the invitee user account based on the importance level. One or more events that the organizer account has access to may be surfaced in an event scheduling assistant user interface associated with the organizer user account.

Intelligent event time bridge across domains

Architecture for generating a temporary account (e.g., an email address) with a user-supplied friendly name and a secret used to the sign the temporary account. For example, when a user wishes to create a temporary email address to use with an online organization, a friendly name is provided and the system generates a temporary email address including the friendly name. A signing component signs the temporary email address with a secret. One or more of these secrets can be provisioned prior to the user's creation of a friendly name, which eliminates propagation delay. During use, only incoming email messages having the temporary email address signed with the secret are validated. When the user revokes the temporary email address, the secret is revoked and the revocation is propagated to network gateways, rejecting any email sent to that address.

Signed ephemeral email addresses

Email-based recovery actions may be provided. A request from a user to perform an action may be received. If the user is determined not to have permission to perform the action, a message may be sent to a second user to approve the requested action. If the second user approves the requested action, the requested action may be performed.

Email-based automated recovery action in a hosted environment

Architecture that enables data handling according to types of social relationships. A social graph is used to categorize the types of the social relationships of the tagged messaging users. The social graph can include social relationship categories for friends, family, coworkers, and blocked individuals of the recipient, for example. The social graph can also include metadata related to the tagged users. The metadata defines the social relationship of the tagged users to the recipient. Delivery of messages to the recipient from the tagged messaging users is managed based on the social graph. Delivery management can include blocking messages, allowing the messages through, or delivering the messages with high or low priority, for example. Email messages can be delivered to respective email locations based on the social graph. User information can be imported and/or mined from external sources to augment the social graph.

Social graphing for data handling and delivery

A multi-level monitoring system is provided for monitoring multiple performance aspects of a cloud service concurrently in order to generate a full and reliable performance analysis of the cloud service. The multi-level monitoring system may include a set of components for carrying out the performance analysis of the cloud service which may be deployed together to operate externally, internally, or concurrently with the cloud service. The component framework of the multi-level monitoring system may include a main component, a plug-in associated with the main component, a definition database, a log database, and an output database. The main components of an example multi-level monitoring framework may include a probe runner component for probing the cloud service, a monitor component for generating alerts based on probe results, and a responder component for processing the alerts and taking appropriate actions to improve the cloud service performance.

System comprising probe runner, monitor, and responder with associated databases for multi-level monitoring of a cloud service

Growing community of inventors

Tacoma, WA, United States of America

Charlie Ricafort Chung