{"id":5125,"date":"2017-03-09T12:03:53","date_gmt":"2017-03-09T17:03:53","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/azuregov\/?p=5125"},"modified":"2017-03-09T12:03:53","modified_gmt":"2017-03-09T17:03:53","slug":"building-a-solution-on-azure-government-part-i-cognitive-services","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/azuregov\/building-a-solution-on-azure-government-part-i-cognitive-services\/","title":{"rendered":"Building a solution on Azure Government Part I: Cognitive Services"},"content":{"rendered":"

The Microsoft Azure Government platform is rapidly innovating with new services being introduced all the time. We have recently announced HDInsight and Power BI as GA on Azure Government. These data-centric services unlock a world of possibilities for your organization to process massive amount of data.<\/p>\n

In this developer-centric walk-through, I will show you how you can leverage Azure Government to implement a Government-focused scenario. In this scenario, we will translate a Chinese document to English and then perform data analytics and visualizations on that translation. This walk-through will consist of 3 major parts:<\/p>\n

    \n
  1. Cognitive Services to translate a Chinese document to English.<\/li>\n
  2. HDInsight to perform data analytics on that translation and produce basic word counts.<\/li>\n
  3. Power BI to visualize the data produced by HDInsight.<\/li>\n<\/ol>\n

    If you prefer, you can follow along with a video walk-through<\/a> of this blog post.<\/p>\n

    Cognitive Services<\/h2>\n

    First, we will use Cognitive Services for document translation. Cognitive Services is currently available in Azure public \u2013 and will soon be available in Azure Government.<\/p>\n

    In the screenshot below, you can see that I already have a Cognitive Services account set up that is specifically for the \u201cTranslator Text API\u201d.<\/p>\n

    \"1\"<\/a><\/p>\n

    We can click the \u201cKeys\u201d tab to see the access keys and we can copy Key 1 to our clipboard.<\/p>\n

    \"2\"<\/a><\/p>\n

    Now that we have our access key, let\u2019s familiarize ourselves with the basic Cognitive Services Translator API. First, we need to get an access token to make our translation calls. Let\u2019s use Postman<\/a> to make our HTTP calls. Postman is a free, cross-platform tool that enables developers to easily make direct calls to HTTP web APIs.<\/p>\n

    We must first call the cognitive services issueToken endpoint to get a bearer token:<\/p>\n

    \"3\"<\/a><\/p>\n

    We execute an HTTP POST to https:\/\/api.cognitive.microsoft.com\/sts\/v1.0\/issueToken<\/strong> while sending the Key we copied from the portal as the Ocp-Apim-Subscription-Key<\/strong> header. This returns a large string that we\u2019ll use as the bearer token. Since we need to send this token on subsequent requests, let\u2019s store it in Postman as a \u201cglobal\u201d to make subsequent calls easier. We\u2019ll store it in a Postman global called \u201ccs-bearer-token\u201d \u2013 the value will be \u201cBearer\u201d followed by a space and the value returned from the issueToken call:<\/p>\n

    \"4\"<\/a><\/p>\n

    Now let\u2019s make a call to the Cognitive Services text translation API. As shown in the screen shot below, we\u2019ll call the \/translate<\/strong> endpoint with the following query string parameters:<\/p>\n