This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
This month, we have promoted three of the client libraries to general availability, and expanded our service support to include a preview SDK for our Cognitive Service: the Azure Text Analytics service.
The new generally available libraries being released this month are:
- Azure App Configuration
- Azure Key Vault Certificates
- Azure Event Hubs, (.NET and Java are pending final validation, but should appear soon!)
These are ready to use in your production applications. You can find details of all released libraries on our releases page.
New preview releases:
We believe these are ready for your use, but not yet ready for production. Between now and the GA release, these libraries may undergo API changes. We'd love your feedback! If you use these libraries and like what you see, or you want to see changes, let us know in the GitHub issues for the appropriate language.
Use the links below to get started with your language of choice. You will notice that all the preview libraries are tagged with "preview".
If you want to dive deep into the content, the release notes linked above and the change logs they point to give more details on what has changed.
The Text Analytics API is part of the Azure Cognitive Services suite of machine learning services that provides advanced natural language processing over raw text. It can be used for sentiment analysis, language detection, key phrase extraction and entity recognition (such as PII).
The new SDK supports all the features of the new v3.0 REST API for Text Analytics. For example, you can detect the language that the text was written in, identify PII (personally identifiable information), extract key phrases, categorize concepts like places and people within the text, link to external sources (like Wikipedia or Bing) for disambiguation, and perform sentiment analysis.
The DefaultAzureCredential() object will use whatever credentials it can find. If you are running on a local development workstation, it will use the user credentials from local development tools like Visual Studio. If you are running the app in the Azure cloud, it will use the connected service principal.
Let's take a typical string and use the Text Analytics API to obfuscate PII within a hypothetical logging method:
The output should be:
The personally identifiable information has been replaced with something innocuous. The SDK has both synchronous and asynchronous methods in all libraries, allowing you the flexiblity to build your app in the way that you prefer.
Let's take a look at another use case - sentiment analysis. Use sentiment analysis to find out what your customers think about the comments that they write in social media or other channels. The API returns a score between 0 and 1 for each document. This time, we will look at a Python example. As before, you need a client reference:
With a reusable client, you can perform any of the text analytics operations:
This gives you an idea of how easy sentiment analysis is to implement, but there is much more power there. For example, you can do per-sentence sentiment analysis.
Working with us and giving feedback
So far, the community has filed hundreds of issues against these new SDKs with feedback randing from documentation issues to API surface area change requests to pointing out failure cases. Please keep that coming. We work in the open on GitHub and you can submit issues here:
Finally, please keep up to date with all the news about the Azure developer experience programs and let us know how we are doing by following @azuresdk.