Microsoft Technology Licensing, LLC

Qin Zhou

Parul Manek

Mohamed Rouatbi

Xin Li

Kevin Gammill

Lei Wang

Zhipeng Zhao

Zubin Alexander

Rajeev Kumar Mittal

Ellery Charlson

Manjusha Madhav Mangaonkar

David Michael Sauntry

Chetan S Shankar

Pradeep Ayyappan Nair

Sandeep Kalarickal

Thomas Charles Knudson

Peter Gregg Miller

Somak Chattopadhyay

Shont Miller

Lu Jin

Maria Black

Elaine Lu

Damien Gallot

Christopher Geisbush

Maisem Ali

Lilei Cui

Yuan-Fen Kuo

Tom Keane

Tony Kao

Siddhartha Pasumarthy

Brian James Hardy

Techniques allow DevOps personnel to perform incident management for cloud computing environments in a manner that maintains control over restricted data and the data plane. The DevOps personnel do not have access to restricted data or the ability to modify the cloud computing environment to gain access to restricted data. The incident management techniques include executing automatic operations to resolve an incident and allowing DevOps personnel to execute remote operations without providing the DevOps personnel access. A further incident management technique provides DevOps personnel with just-in-time (JIT) access that is limited to a certain level or type of access and limited in time. Still another technique for incident management is using an escort model, in which an escort session between operating personnel and DevOps personnel is established and connected to the cloud computing environment to allow the DevOps personnel access to the production environment while escorted by the operating personnel.

Incident management to maintain control of restricted data in cloud computing environments

Described is a technology in which a set of objects represent educational entities of an educational model, with relationships between objects. For example, a course object instance may have a relationship with a task instance and a user instance (such as representing a student). Other objects may include user credentials objects, group objects, degree program objects, course plan objects, institution objects, school objects, and/or department objects. The set of objects may be pre-defined and maintained in a persistent storage; this pre-defined set may be extended with an extended object that has relationships with pre-defined objects. The educational entities of an object model may be maintained in rows of a table, with each row having a field that identifies which entity is represented by that row. The table is accessed to determine relationships between an instantiated object for an entity and at least one other instantiated object for another entity.

Educational entity architecture and object model

The educational adaptive provider architecture described herein provides a way for an educational services framework to be built on varying underlying existing technologies without any changes in the object model and services. The provider framework supports the ability to have multiple types of providers for various services, such as, for example, for authorization, authentication, communication, grouping, scoring, social-networking, storage and user functions. The educational adaptive provider architecture provides easy integration of existing institutional and educational service deployments.

Educational adaptive provider architecture

Growing community of inventors

Kirkland, WA, United States of America

Qin Zhou