blog.atwork.at

news and know-how about microsoft, technology, cloud and more.

Detect sentiment with Text Analytics

Monday, February 25, 2019 8:00 AM Toni Pohl
Azure Cognitive Services offer a bunch of services. One is the Sentiment Analysis API that allows to analyze unstructured text for tasks such as sentiment analysis based on Microsoft machine learning algorithms. See the first steps how to use that here.The test works in the same way with Postman as in the previous article.The goal here is to analyze some text to get a positive or negative result of the meaning.So, we just need some Azure logic and a tool to send and get the data. How to detect sentiment with Text Analytics informs about the service we want to consume. Again, we need to create a new Cognitive Service and to get our own access data from the Azure Portal. Once created, we get that data in the service overview and in the keys menu.Then, calling the Computer Vision API is easy: We need a HTTP POST request against the API and modify just the region and the subscription key.https://<region>.api.cognitive.microsoft.com/analytics/v2.0/sentiment?subscription-key=<subscription-key>So, my sample starts with https://westeurope.api.cognitive.microsoft.com/analytics/v2.0/sentiment...In Postman, we just create a new POST request with that URL and some parameters as here:As Headers we add a key "Content-Type" with value "application/json" and the body text that shall be uploaded with that post.As defined, the data we want to submit can be formatted JSON type, as here. First, there's a positive, then there's a negative text, in english language.{         "documents": [             {                 "language": "en",                 "id": "1",                 "text": "We love this trail and make the trip every year. The views are breathtaking and well worth the hike!"             },             {                 "language": "en",                 "id": "2",                 "text": "Poorly marked trails! I thought we were goners. Worst hike ever."             }         ] }See Language and region support for the Text Analytics API for more info.When clicking on the "Send" button, the request should be sent to the API. After some seconds of analyzing, the result will be shown as body, similar as here. Here's the output in JSON format.{     "documents": [         {             "id": "1",             "score": 0.92014169692993164         },         {             "id": "2",             "score": 0.05087512731552124         }     ],     "errors": [] } The return data says, that the first text with id 1 is positive (92%), the second text with id 2 is very negative (5%). A neutral value would be 0.5 (50%). Happy analyzing your text with the Sentiment Analysis API!
AI | Azure | Cloud | Cognitive Services | Developer | English | Microsoft | Tools
mehr

First steps with the Microsoft Vision API

Monday, February 25, 2019 7:00 AM Toni Pohl
Cloud services help to automate simple and complex processes. For analyzing a picture, the Microsoft Cognitive Services offer a bunch of services like the Vision API, (Custom) Computer Vision, Face API, Video Indexer an more. Follow this first sample with Postman to start with the Vision API.
Azure | AI | Cognitive Services | Cloud | Developer | English | Microsoft | Tools
mehr

Troubleshooting Delegate365-Login

Thursday, February 21, 2019 5:00 PM Toni Pohl
Sometimes support cases are opened because users cannot login to Delegate365 with their Office 365 account. In most cases, the browser cache automatically signs-in a user with wrong credentials. Please follow these simple steps to see how to achieve a successful login to the Delegate365 portal in such scenarios.
Delegate365 | English | Microsoft | Microsoft365 | Office365 | atwork
mehr

Groups Governance Toolkit Part 4-Ownerless Groups

Wednesday, February 13, 2019 4:00 PM Martina Grom
In this multi-part series we show you how to handle the Office 365 Groups and Microsoft Teams governance toolkit. The next article cover the governance part of our Groups Governance Toolkit.Imagine your company policy requires at least 2 owners per Office 365 Group or per Microsoft Team. In this part, we want to monitor all groups that are ownerless (orphaned), or do not comply with our organization's policies. The IT department shall get the information of all groups and teams where there are no owners or not enough owners and the possibility to fix that. Read below how this can be accomplished.
atwork | Azure | Cloud | Developer | DevOps | English | Flow | GitHub | Governance | Logic apps | Microsoft | Microsoft Teams | Microsoft365 | Office365 | PowerShell | Tools
mehr

Ready for European Collaboration Summit 2019!

Friday, January 25, 2019 3:00 PM Toni Pohl
Join us at the legendary European Collaboration Summit from May 27 to May 29, 2019 in Wiesbaden, Germany! #collabsummit is Europe's largest community-driven conference with a focus on modern workplace technologies and digital transformation, with topics such as Microsoft 365, Azure, SharePoint, AWS, and Business Apps. The conference is organized for the community by the community.
Azure | Blog | Cloud | Business Intelligence | Developer | English | Event | Microsoft | MVP | Office365 | atwork
mehr

Groups Governance Toolkit Part 3-Develop Azure Functions

Wednesday, January 16, 2019 4:00 PM Martina Grom
After the introduction of the Office 365 Groups and Microsoft Teams Governance Toolkit and with the necessary requirements we are now looking into Azure Functions. In our group and team provisioning scenario, we need a little code for provisioning of an Office 365 group and a Microsoft team. Serverless computing with an Azure Function provides the optimal solution for that. Follow these steps to create the function we need for our workflow.
atwork | Azure | Cloud | Developer | English | Flow | GitHub | Governance | Logic apps | Microsoft | Microsoft Teams | Microsoft365 | MVP | Office365 | PowerShell | Tools
mehr

Groups Governance Toolkit Part 2-Provisioning requirements

Friday, January 11, 2019 5:00 PM Martina Grom
In part 1 of this series we described the scenario for our Office 365 groups governance toolkit. In this part we will setup a workflow for the Office 365 and Microsoft Teams provisioning. Workflows help to follow specific processes for a successful collaboration.
Offering self-services for users is a key to reduce workloads on the IT department and to allow users to cover their requirements quickly while the organization's policies are enforced during the process. A frequently asked request is how to provision a new Microsoft Team in Office 365 in a secure and monitored way. See how this can be implemented here.
To allow an app to create a Microsoft group or team programmatically in a workflow, we will use the Microsoft Graph API, Azure Functions and Flow or Logic Apps. With these technologies, we can create powerful workflows to offer a self-service for users to create a team when needed, approved by the manager and being provisioned with all the necessary properties and permissions.
atwork | Azure | Cloud | Developer | English | Flow | GitHub | Governance | Graph | Logic apps | Microsoft | Microsoft Teams | Microsoft365 | MVP | Office365 | PowerShell | SharePoint | Tools | Yammer
mehr

Groups Governance Toolkit Part 1-Overview

Tuesday, January 8, 2019 5:00 PM Martina Grom
IT-Governance is an important topic, especially in large organizations. At Microsoft Ignite conference, we showed the "Groups Governance Toolkit" with a bunch of useful tools to regulate and monitor Office 365 groups and Microsoft Teams. Here, we will show the step-by-step guidance how to implement that toolkit with Microsoft 365 and Microsoft Azure. Let's start with an overview what topics we cover in this article series.
atwork | Azure | Cloud | Developer | English | Governance | Graph | Logic apps | Microsoft | Microsoft Teams | Microsoft365 | MVP | Office365 | PowerShell | SharePoint | Tools | Yammer
mehr