Microsoft Technology Licensing, LLC

Roshane Silva

Eric B Fox

Patrick Simek

Kfir Ami-ad

Gokhan Uluderya

Tyler Furtwangler

Bijul Soni

Sanjay Rama

Le Chang

Kalyan K Kona

Zohar Raz

Mangalam Rathinasabapathy

Harpreet Miglani

Xinghuo Zeng

Jun Zhang

Brian G O'Connor

Balinder Malhi

Darius Snapkauskas

Randy David Thomson

Min Shao

Jianfeng Cai

Atanu Banerjee

Neetha Sumana Tuluri

Prashant Gaurav

Sundar Paranthaman

Brad Smith

Fuyuan Bie

Dexter Dauz

Nick Alfeo

Morten Haavaldsen

Brian Gregory O'connor

The techniques described herein facilitate scope-based certificate deployment for secure dedicated tenant access in multi-tenant, cloud-based content and collaboration environments. In some embodiments, a method is described that includes receiving an incoming authentication request from an access system, wherein the authentication request includes metadata, extracting the metadata from the authentication request, and processing the metadata to identify a tenant corresponding to the request. A tenant-specific certificate associated with the tenant is then accessed and provided to the access system for validation by a third-party certificate authority.

Scope-based certificate deployment

Various systems and methods for domain authentication are described herein. In an example, the method may include detecting a domain from a request of a tenant for access to a farm. The method may also include identifying a presence of a site ID from a database of the farm based on the domain. The method may also include sending an authentication request to a default site or a custom site, the authentication request managed through a site manager based on the identified presence of the site ID in the database of the farm. The method may also include routing traffic from the tenant to the farm in response to satisfaction of the authentication request.

Domain authentication

In one example, a server farm patching system may wait until fewer users are accessing a server farm to apply a patch code set to a server application executed by a server at the server farm. The server farm patching system may identify an off-peak usage time range for a server farm describing when the server farm has an activity level below an activity threshold. The server farm patching system may apply a patch code set at an off-peak usage patching aggressiveness level indicating an off-peak upper bound percentage of servers in the server farm receiving the patch code set when within the off-peak usage time range. The server farm patching system may apply the patch code set at a peak usage patching aggressiveness level indicating a peak upper bound percentage of servers in the server farm receiving the patch code set when outside the off-peak usage time range.

Off-peak patching for enterprise stability

A cyclical patching process associated with a cloud application may be defined to ensure high availability (HA) of the cloud application in order to prevent impacting an availability to end users. A list of server identities corresponding to one or more servers of a datacenter hosting the cloud application may be accepted. HA metric values for each of the server identities may be determined in order to compute an overall HA metric value for the cloud application. A subset of the servers may be removed from a rotation framework of the cloud application based on the determined HA metric values, where the removal does not affect the overall HA metric value of the cloud application. One or more patches may be applied to each server within the subset of servers in parallel, and the subset of servers may be reinstated in the rotation framework of the cloud application.

Patch process ensuring high availability of cloud application

In one embodiment, a network system may be upgraded without losing access to write privileges to a network fileduring the system upgrade. A network file management systemmay execute a system upgrade. A network file management systemmay provide direct write access for a data fileto a user throughout the system upgrade.

Seamless upgrade for network system

Requests to a server farm are managed in an application intelligent manner based on server health and client information. A request management (RM) module is configured to make smart routing decisions, based on routing rules that relate the nature of requests to a dynamic topology of a server infrastructure. The RM may use its knowledge of server applications, servers, and clients to deny potentially harmful requests from entering the service, route good requests to the suitable machines, and maintain a history of the decisions and consequences automatic and/or manual optimization.

Application intelligent request management based on server health and client information

Server health and client information are exchanged through headers for request management. Headers in standardized or proprietary protocol communication between servers and a request management module and/or clients and the request management module may be used to exchange server health and client information. The exchanged server health and/or client information may be employed in throttling, routing, and/or load balancing the incoming requests. Rules specified by the client through the header exchange may also be used for throttling, routing, and/or load balancing decisions.

Exchange of server health and client information through headers for request management

Growing community of inventors

Seattle, WA, United States of America

Roshane Silva