Microsoft Technology Licensing, LLC

Chetan Pentam Raghavendra

Dmitri A Klementiev

Varun Jain

Dhruv Gakkhar

Michail Zervos

Satya Sudha Kolluru

Lenina Devi Thangavel

A system includes: at least one processor running instances of two or more services. Instances of a first service are dependent upon instances of a second service. A fault-injection manager, based on data in a service directory indicative of dependencies of services of the system, determines a fault-inducing condition to inject into the system and injects the fault-inducing condition into the system. A health monitoring manager detects failures in the system and identifies the first service as vulnerable to the fault-inducing condition when the fault-inducing condition causes an instance of the second service to fail.

Service directory and fault injection management systems and methods

Providing rich contextual information to a user in an authentication agnostic way with respect to the user. A method includes, at an application, receiving a request from a first user to access functionality of the application. The request from the first user comprises information identifying a second user who has consented to their social media information being used by the application. The method further includes sending information to the identity provider which includes information identifying the second user. The identity provider is managed by an entity separate from the application. The method further includes receiving, at the application, social media information common between the first user and the second user. The method further includes providing at least a portion of the common social media information, to the first user, in an authentication agnostic way with respect to the first user's authentication to the application.

Seamless viral adaption

A network entity that allows collaboration among end users of a collaborative application by using different identifiers. The network entity receives an authentication request from a collaborative application to authenticate an end user. The network entity uses a first identifier of the end user that is associated with the network entity to verify that end user is permitted to use the collaborative application and informs the collaborative application that the end user is permitted to use the collaborative application. The network entity receives from the collaborative application a second identifier of the end user that is not associated with the network entity. The second identifier is linked to the first identifier. The network entity allows the second identifier to be used to authenticate the user with the collaborative application without the need to use the first identifier when a collaborative session is begun.

Linking identities in a network entity

Systems and methods disclosed herein are directed to creating a service directory of dependencies for services running on a system, wherein instances of a first service are dependent upon instances of a second service. The directory of dependencies comprises metadata associated with connections between the services. The system injects faults targeting all levels of the dependencies. The system is monitored to detect failures created by the faults. The injected faults are selected from transport layer faults, memory pressure, processor pressure, storage pressure, virtual machine restart, and virtual machine shut down. A domain name service is monitored to identify names that are resolved for the services. The service directory is then updated continuously with additional dependencies using information about the resolved names. The faults may be injected in a guided manner, wherein the scope of the faults is increased in steps over time to identify a failure point in the system.

Growing community of inventors

Kirkland, WA, United States of America

Chetan Pentam Raghavendra