Microsoft Technology Licensing, LLC

Viktoriya Taranov

Alexander Hopmann

Nikita Voronkov

Puneet Narula

Daniel Blood

Tarkan Sevilmis

Siddharth Rajendra Shah

Pedro Dantas DeRose

Bhavesh Anil Doshi

Ramanathan Somasundaram

Artsiom Kokhan

Victor Poznanski

Jonathan Campbell

Zhenguang Chen

Charles Reeves Little, Ii

Boxin Li

Arun Keller Krishnamoorthy

Charles Keller Smith

Brian William Timm

Andrew Joseph Violino

Jonathan Reed Harris

Ashok Kuppusamy

Jaclyn Carley Knapp

Jesse Daniel Eskes Rusak

Richard Leigh Mains

Chad Steven Estes

Michael Francis Palermiti, Ii

Jayant Sivarama Krishnamurthy

Allison Anne O'Mahony

Harris Syed

Fredrik Holm

David Ernesto Heekin Burkett

Diego Hernan Carlomagno

Talon Edward Ireland

Jose Miguel Rady Allende

Tudor Buzasu Klein

Sergiy Gavrylenko

Dmitriy Meyerzon

Patrick Miller

Yauhen Shnitko

James Squires Masson

Michal Krzysztof Piaseczny

Gerhard A Schobbe

Daniel E Kogan

Andrew Paul McGovern

Glen Buhlmann

Gautam Vishwas Vaidya

Gunawan Herri

Sid R Shah

Kai Yiu Luk

Antonio Marcos Da Silva, Jr

Andrew Paul Mcgovern

Antonio Marco Da Silva

Antonio Marcos Da Silva

Various embodiments discussed herein enable client applications to be heavily integrated with a voice assistant in order to perform commands associated with voice utterances of users via voice assistant functionality and also seamlessly cause client applications to automatically perform native functions as part of executing the voice utterance. Such heavy integration also allows particular embodiments to support multi-modal input from a user for a single conversational interaction. In this way, client application user interface interactions, such as clicks, touch gestures, or text inputs are executed alternative or in addition to the voice utterances.

Voice assistant-enabled client application with user view context and multi-modal input support

A secondary location is configured as a recovery service for a primary location of the service. The secondary location is maintained in a warm state that is configured to replace the primary location in a case of a failover. During normal operation, the secondary location is automatically updated to reflect a current state of the primary location that is actively servicing user load. Content changes to the primary location are automatically reflected to the secondary location. System changes applied to the primary location are automatically applied to the secondary location. For example, removing/adding machines, updating machine/role assignments, removing adding/database are automatically applied to the secondary location such that the secondary location substantially mirrors the primary location. After a failover to the secondary location, the secondary location becomes the primary location and begins to actively service the user load.

Automatic configuration of a recovery service

Rules, such as condition-action rules, are configured at different levels of a hierarchy. For example, a top level site administrator may configure rules, lower level administrators may configure rules and end users may configure rules. Rules created at a higher hierarchical level are automatically inherited by lower hierarchical levels in the same branch of the hierarchy. The source of the inherited rule is indicated with its display such that the hierarchical level of creation can readily be determined. The inherited rule(s) may be toggled on/off at the lower hierarchical levels but edits to inherited rule(s) are restricted. Instead, a copy of any inherited rule may be made to create a local copy of the rule that is editable. Rules may be ordered and when a lower hierarchical level inherits the rules, the ordering is preserved.

Inheritance of rules across hierarchical levels

A set of user interfaces is provided to an administrator of a website. The user interfaces enable the administrator to configure search functionality of the website to present different types of search results differently. For instance, the administrator can use the user interfaces to configure the search functionality to present different properties for search results belonging to different result types.

Result types for conditional data display

Rules, such as condition-action rules, are configured at different levels of a hierarchy. For example, a top level site administrator may configure rules, lower level administrators may configure rules and end users may configure rules. Rules created at a higher hierarchical level are automatically inherited by lower hierarchical levels in the same branch of the hierarchy. The source of the inherited rule is indicated with its display such that the hierarchical level of creation can readily be determined. The inherited rule(s) may be toggled on/off at the lower hierarchical levels but edits to inherited rule(s) are restricted. Instead, a copy of any inherited rule may be made to create a local copy of the rule that is editable. Rules may be ordered and when a lower hierarchical level inherits the rules, the ordering is preserved. The lower level may toggle on/off the execution of each rule within the ordering.

Inheritance of rules across hierarchical level

Systems and method for routing search query results in a networked computing environment. An initial search query is reformulated into at least one sub-query in accordance with one or more configurable rules. The sub-query is sent to at least one information system or source, and any potential hits associated with the same are optionally combined and then rendered for viewing.

Routing query results

Rules, such as condition-action rules, are configured at different levels of a hierarchy. Rules created at a higher hierarchical level are automatically inherited by lower hierarchical levels in the same branch of the hierarchy. The source of the inherited rule is indicated with its display such that the hierarchical level of creation can readily be determined. The inherited rule(s) may be toggled on/off at the lower hierarchical levels but edits to inherited rule(s) are restricted. Instead, a copy of any inherited rule may be made to create a local copy of the rule that is editable. Rules may be ordered and when a lower hierarchical level inherits the rules, the ordering is preserved. While the ordering of any rules remains constant when inherited at the lower levels, the lower level may toggle on/off the execution of each rule within the ordering.

Jobs submitted to a primary location of a service within a period of time before and/or after a fail-over event are determined and are resubmitted to a secondary location of the service. For example, jobs that are submitted fifteen minutes before the fail-over event and jobs that are submitted to the primary network before the fail-over to the second location is completed are resubmitted at the secondary location. After the fail-over event occurs, the jobs are updated with the secondary network that is taking the place of the primary location of the service. A mapping of job input parameters (e.g. identifiers and/or secrets) from the primary location to the secondary location are used by the jobs when they are resubmitted to the secondary location. Each job determines what changes are to be made to the job request based on the job being resubmitted.

Replaying jobs at a secondary location of a service

Rules, such as condition-action rules, are configured at different levels of a hierarchy. For example, a top level site administrator may configure rules, lower level administrators may configure rules and end users may configure rules. Rules created at a higher hierarchical level are automatically inherited by lower hierarchical levels in the same branch of the hierarchy. The source of the inherited rule is indicated with its display such that the hierarchical level of creation can readily be determined. The inherited rule(s) may be toggled on/off at the lower hierarchical levels but edits to inherited rule(s) are restricted. Instead, a copy of any inherited rule may be made to create a local copy of the rule that is editable. Rules may be ordered and when a lower hierarchical level inherits the rules, the ordering is preserved. While the ordering of any rules remains constant when inherited at the lower levels, the lower level may toggle on/off the execution of each rule within the ordering.

Growing community of inventors

Bellevue, WA, United States of America

Viktoriya Taranov