Microsoft Technology Licensing, LLC

Krishna C Vitaldevara

Eliot Carleton Gillum

Jason D Walter

Mehrdad Bidgoli

Luke Abrams

David Steeves

Vasantha K Vemula

Yordan Ivanov Rouskov

Eric Fleischman

Malcolm Hollis Davis

Ramesh Manne

Prabu Raju

Winfred Wong

Hersh Dangayach

Payoj Baral

Meenakshi Ramaswamy

Niyantha Shekar

Geoffrey John Hulten

Douglas John Hines

Robert L McCann

Mihai Costea

Milenko Drinic

Fang Yu

Martin Abadi

Wei Jiang

Yinglian Xie

Ke Wang

Xiaolong Li

Zhen Wei

Ivan Osipkov

Tyler J Schnoebelen

Ram Pratap Singh

Leela Tamma

Sridhar Raman

Kevin H Lau

Michael James Ahiakpor

Jagadeesh Kunda

Paul M Midgen

Samuel J L Albert

Ananth Inamti Sundararaj

Aravind K Ramachandran

Rebecca Ping Zhu

Sanchan Sahai Saxena

Zhuoqing Morley Mao

Ariel Nicolas Gordon

Qifa Ke

Aleksander R Kolcz

Ryan M Burkhardt

Pui-Yin Winfred Wong

Ryan Charles Colvin

Chad W Mills

Joshua Korb

Aby John

Richard Craddock

Yuxiang Xu

Durgesh Srivastava

Harsh Satyanarayan Dangayach

Junxian Huang

Robert Lee Mccann

Luke T Abrams

Pui-Yin Wong

Joshua David Korb

Message management and classification techniques are described. In one or more implementations, a message received from a sender for delivery via a user account is examined to extract one or more features of the message. A determination is then made as to whether the message corresponds to one or more categories based on the extracted features, the categories usable to enable features to be applied to the message in a user interface.

Message classification and management

In one embodiment, a user authentication server may use geo-location tracking to determine whether to present an enhanced identity challenge. A communication interfacemay receive a user login attempt by a user and a current location of the user login attempt. A data storagemay store a user location profile of the user. A processormay execute a comparison of the current location to the user location profile. The communication interfacemay present the user with an enhanced identity challenge before allowing user access based on the comparison.

Protection from unfamiliar login locations

In representative embodiments, multiple cloud computing infrastructures, each having its own application and management fabric, coexist with in the same cloud computing infrastructure. This results in a cloud computing infrastructure where multiple management fabrics and application fabrics coexist to offer their own services and cross platform services. Each functions independently and also communicates with each other to offer high availability and disaster recovery. One application and management infrastructure is a host to the other application and management infrastructure. The hosted infrastructure accesses underlying fabrics through the host infrastructure. A resultant system comprises a common hardware fabric, a common runtime, and a service fabric comprising services from both the host and hosted infrastructures.

Multi-service application fabric architecture

Techniques involving identification of electronic messages that are the first contact between the sender identification and addressed recipients. One representative technique includes identifying electronic messages originating from a sender that are first contact electronic messages between the sender and targeted recipients. The sender of the electronic messages may be designated as a source of unsolicited messages if heuristics involving the first contact electronic messages indicate a distribution of unsolicited messages by the sender.

Identifying first contact unsolicited communications

Email tags are described. In embodiments, email messages are received for distribution to client devices that correspond to respective recipients of the email messages. Email routing decisions are applied to route an email message to an email folder for a recipient of the email message, where the email folder may include an email inbox, a junk folder, or a user-created folder. The email message is then tagged with an email tag to generate a tagged email message. The email tag includes a routing description that indicates why the email message was routed to the particular email folder.

Email tags

In one embodiment, a cloud service interfaceor a device interfacemay filter messages in a message synchronization between a message service account and a cloud service account. A cloud service interfaceor a device interfacemay associate a message service accounton a user messaging devicewith a cloud service account. The cloud service interfaceor a device interfacemay execute a message synchronization between the cloud service accountand the message service account. The cloud service interfaceor a device interfacemay apply a message filter to the message synchronization.

Safety protocols for messaging service-enabled cloud services

Geo-data spam filters are described. In one or more implementations, origin data and language data of a message are evaluated to establish a score for the message indicating a likelihood that the message is spam. The evaluation includes comparing the origin data and the language data to ranked lists indicating message origins and languages with which a respective message recipient interacts positively and ranked lists indicating message origins and languages with which the respective recipient interacts negatively. Interactions of the respective recipient with previously sent messages may be tracked to form these lists. Based on the score established by evaluating the origin data and the language data of the message, the message is filtered for delivery.

Geo-data spam filter

When a user account is in an alternate (fault) state, communication or sync between an application provider and a device or client application typically is interrupted. When parties do not support rich fault messaging, communication of the reason for the interruption and remediation steps has been impossible. An application server provides rich fault messaging using applications that do not provide explicit error messaging and protocols that do not provide explicit error messaging without changing either the application or the protocol by additional interactions between an identity provider and the application server. The application server uses authentication state information provided by the identity server to generate a notification sync event that appears to the application and the protocol to be a normal sync event. The notification sync event is used to provide the user with information needed to determine what the problem with the account is and how to fix it.

Communicating state information to legacy clients using legacy protocols

Growing community of inventors

Santa Clara, CA, United States of America

Krishna C Vitaldevara