Microsoft Technology Licensing, LLC

Productiv, Inc.

Suresh Parameshwar

Ashish Aggarwal

Shantanu Kumar

Mengsu Chen

Aditya Jayan

Sridhar Srinivasan

Darren Alexander Apfel

Sarthak D Shah

Thomas Anand Jeyaseelan

Bhalakumaaran Erode Ranganathan

Keizo Fujiwara

Lan Tang

Smriti Yamini

Nissim Natanov

Alexander Marliave Hehmeyer

Jianfeng Yan

Nicholas A Bigelow

Maryam Khabazan

Zhou Xiang

Zankar P Thakkar

Misrak G Ararso

Shoaev S Hares

Niraj S Khanchandani

Ling Yu

Fei Dai

Aditi Saha Aditi

Pranathi Venkatayogi

A software as a service (SaaS) management platform, includes: an uploader process for receiving a plurality of contract files relating to purchases of a SaaS application; parsing logic that identifies terms in the plurality of contract files; normalization logic for assigning a normalization SKU to respective contract files based on the terms identified in the respective contract files; a background process that generates anonymized contract data by storing the terms of each contract file in association with the normalization SKU assigned to the contract file in an anonymous manner; a backend process that, responsive to a request from a client device, accesses the anonymized contract data to generate a distribution of terms of the anonymized contract data, generates benchmark data identifying an approximate location of terms of a given customer's contract file within the distribution, and returns the benchmark data to the client device for rendering through a user interface.

SaaS application contract terms benchmarking in a SaaS management platform

A method implemented in a software as a service (SaaS) management platform, includes: receiving a plurality of contract files relating to purchases of a SaaS application; identifying terms in the plurality of contract files; assigning a normalization SKU to respective contract files based on the terms identified in the respective contract files; generating anonymized contract data by storing the terms of each contract file in association with the normalization SKU assigned to the contract file in an anonymous manner; responsive to a request from a client device, accessing the anonymized contract data to generate a distribution of terms of the anonymized contract data, generating benchmark data identifying an approximate location of terms of a given customer's contract file within the distribution, and returning the benchmark data to the client device for rendering through a user interface.

Techniques for identity management for permissions are described. According to various embodiments, a user establishes a communication relationship with another user, referred to herein as a 'contact.' According to various embodiments, the contact is associated with multiple identities. Accordingly, embodiments discussed herein enable a primary identity to be specified such that permissions for the primary identity are enforced for interactions with the contact. Further, techniques discussed herein enable a primary identity to be updated based on a change in identity state of a contact.

Identities and permissions

The automated validation of one or more test cases in a validation pass. The validation pass is enabled using a plurality of scenario runners, which are executable components that respond to instructions to run one or more scenarios of a validation pass by beginning to run through such scenarios during the validation pass. The validation pass may be associated with a maximum time such that upper limits on how long the scenario runners may run is set. This likewise limits the time it takes to validate the results of the scenario. The scenario runners provide events that occur during the running of their respective scenarios into an event collector. The events of the validation pass may then be evaluated against one or more test cases to determine whether or not the events have a state indicative of a success or failure of each test cases.

Validation using scenario runners

Described is a pipeline for handling notification messages sent to a mobile messaging message (e.g., SMS or SMTP) recipient, and handling a reply to that notification message, including correlating the notification message with the reply. An engine receives a notification message, and for a notification message to which a reply is possible, maintains state data for use in correlating a received reply with the notification message. The state data includes metadata that indicates that text or code data is expected in any reply. For a reply providing code data, the engine calls a selected URL corresponding to the code. To facilitate message delivery, the engine may format the notification message, including shortening a URL of the message, and/or splitting a longer notification message into shorter notification messages.

Mobile messaging message notifications processing

A strategy is described for forwarding content accessed using a first device to a second device. For instance, the first device can comprise a personal computer and the second device can comprise a mobile telephone. The strategy employs general purpose content-forwarding (CF) functionality. Different providers of content can rely on the same general purpose CF functionality to forward content to the second device, without requiring time-intensive and cumbersome manual modification of the CF functionality for each application.

Strategies for sending content to a target device

Growing community of inventors

Redmond, WA, United States of America

Suresh Parameshwar