I have created 2 resources on Azure, 1 is LUIS Authoring Resource and other is Cognitive Services resource. Then created a LUIS app and deployed it.
I'm trying to use the Bing Spell Check feature on the LUIS but it doesn't seem to work.
URL: https://westus.api.cognitive.microsoft.com/luis/v2.0/apps/<APP_ID>?spellCheck=true&bing-spell-check-subscription-key=<KEY>&verbose=true&timezoneOffset=330&subscription-key=<KEY>&q=I%20hav%20not%20recieved%20statment
Am I missing anything here?
Related
I have an Azure Language Studio Orchestration Projects in https://language.cognitive.azure.com/orchestration/projects
I have a LUIS app in https://www.luis.ai/
Screencap: https://ibb.co/D1tCNM5
When I try to add a Schema Definition, the LUIS is not showing.
Screencap: https://ibb.co/c6cXqKh
Both the Language and LUIS are created with same Tenant.
What could be the issue?
Below is from FAQ. But I recreated everything in west Europe, I still cannot see the LUIS project in Orchestration.
In LUIS, I also cannot see the Language resource when changing the Authoring resource.
https://learn.microsoft.com/en-us/azure/cognitive-services/language-service/orchestration-workflow/faq
Which LUIS applications can I connect to in orchestration workflow projects?
LUIS applications that use the Language resource as their authoring resource will be available for connection. You can only connect to LUIS applications that are owned by the same resource. This option will only be available for resources in West Europe, as it's the only common available region between LUIS and CLU.
I have an Dotnet Core API application which uses IdentityServer4 as IDP. The frontend is built in Angular.
Now, I need to connect to Successfactors of one of my client. I understand SAML is the best federation protocol there.
Please suggest what should be my approach here and relevant tutorials that I can follow. I am not getting good google results.
You need a SAML stack.
Microsoft does not have one. So you need to integrate a third-party product.
There are a number of examples here.
I am trying to develop a simple customer connector for my website on microsoft flow and so far I can't see how to use a web API that is hosted on my website every article tutorial I am coming by require APIs to be hosted on Azure, also an Azure account is a prerequisite .. is it true Only azure APIs to be used for custom connectors ?
Azure is not a prerequisite for Custom Connector. I agree that most of the tutorials talk about connecting Azure hosted apps.
Microsoft flow currently supports creating custom connector with Swagger API output or postman exported data. I created a Postman collection with the API and gave the exported data as input to Microsoft flow for creating the connector.
Detailed Tutorial is available here
https://flow.microsoft.com/en-us/documentation/postman-collection/
I have the same issue, I have configured a custom connector for testing to go against this test / mock API
POST -> https://jsonplaceholder.typicode.com/posts
In the connector test it keep on hitting this URL:
https://msmanaged-na.azure-apim.net/apim/zoom.2dtest.2d002.5f43ed1d930148619c.5f4fd64f4beaca2b60/51136e9557bf4e128e0d7552ff624ebd/posts
I have never configure it to go there. No document explains how or why this would happen.
I have been searching the internet for ways to access the AdSense API via R and have not been able to find documentation. It uses REST with OAuth 2.0.
I am looking to use the API for reporting.
There's a client library to access the Prediction API with R. Prediction and the AdSense Management API are both REST and use Oauth2 so it should be easy to modify the code at:
https://code.google.com/p/google-prediction-api-r-client/
I need a bit of help implementing an OAuth 2 provider for a rest service built on the new ASP.NET Web API. I'm aware there are some similar questions on Stack Overflow but they're more or less links to OAuth libraries. What I'd really like is some sample code or a sample project to get my started. Can anyone point me in the right direction?
I'm looking at DotNotOpenAuth and I believe the 4.0 beta supports OAuth 2 providers. Unfortunately I can't seem to find any code demonstrating how to implement it.
What I need some assistance with is actually getting a 2.0 provider up and running. Once I have that it should be easy enough to integrate it via a HTTP Module or a filter.
I'm interested in 2 legged authentication for API to API communication.
Until DotNetOpenAuth ships a distribution that includes OAuth 2 and the samples together, the best you can do is install the DNOA 4.0 resource server and authorization server roles via NuGet, and then check out the resource server and authorization server samples on GitHub.
But there are currently no samples for the "client secret" grant type, which is the one that best fits your "2 legged" concept for API-to-API communication. In fact the library itself doesn't (yet) support it, but the next NuGet release will and should be available in the next week or so.