Microsoft Translation API Authentication Failure - azure

We currently have both a TEST and DEV environment of our application set to connect to Microsoft Translator. For our test environment, everything connects fine. For our DEV environment, authentication is failing and we do not know why. Both machines appear to have the same configuration. We are testing both with the same API key (which we have done in the past).
My question is: How do we monitor the calls to this API in the Azure portal? I have turned on a number of diagnostics but none are appearing to give me the network info I need. Network Watcher appears to be for VMs. I want to be able to look at the calls that are logged using my key to troubleshoot this issue.
Any help is greatly appreciated :)
Thanks.

You can try application insights - https://learn.microsoft.com/en-us/azure/azure-monitor/app/app-insights-overview
I need some more information about this case,
01. Are you calling Microsoft Translate API inside your application or you are developing an API using, Microsoft Translate API ?
02.Hope you are using azure web apps. Are you using slots to manage dev and test environment.
03. Are you using API Management ?

Related

Can I use google cloud speech api in microsoft azure vm?

I am trying to use google cloud speech API in microsoft azure machine(Where I have installed asterisk service). Is it possible to do this. Because in GCP we have an option where we can enable 'Allow all cloud API services'. But in microsoft we do not have an option to enable. If I use I am getting the following error. Please go through the staktrace and help me.
Note : we have a working version in GCP machine. Now I am deploying it into microsoft vm(Then only I am getting this error).
An API can be called over the internet. If the machine is configured to be able to connect to the internet than yes, you can.
Looking at the error you're getting, it looks like there's something wrong with your authentication setup.
DefaultCredentialsError: Could not automatically determine credentials. Please set GOOGLE_APPLICATION_CREDENTIALS or explicitly create credentials and re-run the application.
For more information, please see https://cloud.google.com/docs/authentication/getting-started
If you follow the instructions in the linked documentation on Getting Started with Authentication, you should be good to go.
Seams like i answered same less than week ago.
Please check that you setuped credentials for asterisk user, not for root. Asterisk is running under asterisk user.

HTTP 500 error using Azure Easytables with Node.js backend

Having created a mobile app in Azure using EasyTables with a Node.js backend, I get an HTTP 500 error trying to post a new item.
Log in to the Azure console and in the project backend run:
npm i sqlite3
That fixes it.
(Answering my own question because I couldn't find this anywhere on StackOverflow. Props to #benjamintam from Readify for the solution)
If your mobile app application is running on Azure cloud not on locally, the issue is a little odd, as the sqlite 3 supporting is for Azure Mobile Apps development on local. You can refer to https://azure.github.io/azure-mobile-apps-node/module-azure-mobile-apps_src_configuration_DataProviders.html for the detailed description.
If your issue occurs on your Mobile Apps running on Azure, please double check whether you have completed the project's initialization. You can refer to https://azure.microsoft.com/en-us/documentation/articles/app-service-mobile-android-get-started/#configure-the-server-project for the steps.
Meanwhile, you can manually add the data connection to Azure SQL in the Azure portal,
And if successfully, you can find the configuration MS_TableConnectionString in Application settings in your Mobile Apps.
Any further concern, please feel free to let me know.

Azure Mobile App malfunctioning after migration

A couple weeks back our Mobile App was migrated from the old portal to the new one and it hasn't behaved properly since.
Our main issues are:
We cannot access any logs files, the tab for Diagnostics logs stopped working entirely on Wednesday but even before that we never got any useful data out of this. When something goes wrong with our nodejs backend we can't find any clue as to what went wrong like we could in our old portal under the logs tab.
We are unable to access the FTP server entirely, it just won't let us login even though the credentials are correct and have been reset multiple times in attempts to get them working.
The server is throwing errors about not having enough disk space left even though we should have 53Gb to go (we're currently using 1.05Gb out of 55Gb)
Our deployments slots are not working at all, when we push our code to the deployment slot it just doesn't work, every request we make to the deployment slots tells us we're not allowed to do anything.
We are running a standard tier Mobile App server. The backend is in NodeJS, our CMS is in ASP.Net and our app itself is in Xamarin Forms.
The issues started after we migrated the server a couple weeks back from the manage.azure.com portal to portal.azure.com.
What can we do?
Edit:
We got through to Microsoft via the payed support plan which we're getting refunded because these are basic functionalities which don't work as advertised after the migration. I've got a call with them in about three hours to get things sorted, if I learn anything we can do ourselves I will update this post to share the knowledge.
This needs to be a support request to Microsoft.
If you can, open an incident with Microsoft Support. If you can't, post a question in the MSDN Community Forum. (We need to ask about particulars of your site and that isn't an appropriate topic for SO)
As the architecture of Mobile Apps is changed from Mobile Services, now the mobile apps migrate to Azure App Services.
Actually the Mobile Apps backend in Node.js is an expressjs project, and the mobile app sdk for node is a middleware of express. So the way for diagnostics and troubleshooting has changed from before we use Mobile Service. You can refer to https://azure.microsoft.com/en-us/documentation/articles/app-service-mobile-node-backend-how-to-use-server-sdk/#Debugging for details about Debugging and troubleshooting for mobile services.
Additionally, we can leverage the Visual Studio Team Services editor as the section How to: Edit code in Visual Studio Team Services shows in the link above, we can monitor the output of the Mobile Apps backend application. E.G:
About your FTP issue, please double check your deployment Username, when we login to FTP server on Azure, we need to input the full FTP user name which is "app\username":
You can refer to https://azure.microsoft.com/en-us/documentation/articles/web-sites-configure/#enabling-diagnostic-logs for details.

Get Azure Dashboard data via api

Scenario:
One team had built one application, and application is running on azure.
maintenance is taken care by same team, we don't want to give full access of production instance to developer team, but want to give read permission, like - monitoring of logs, cpu usages etc.
Solution according to me is build an application which will get dashboard data and log data from azure via api and that data will be displayed to development team.
I am referring these 2 links
https://msdn.microsoft.com/en-us/library/azure/dn722415.aspx
https://azure.microsoft.com/en-in/documentation/articles/api-management-get-started/
Question:
Still I am not able to find api which will give the dashboard data. if anyone know api for the same, please help.
Is there any alternative solution for this scenario.
If you deploy your app using the new Azure Resource Manager mode, it provides a Role Based Access Control to your resources. You can deploy your app inside a Resource Group and provide read access to your developers. They will be able to view the information about the services that your app are made of but without the option to change anything.
This session from Build 2015 can help you to understand what ARM is and what you can do with it: https://channel9.msdn.com/Events/Build/2015/2-659

How do you create an Azure deployable WebRole that use LiveId and Access Control Service

I need some help with creating a simple WebRole that uses federated authorzation/authentication with LiveId and the Access Control Service. I'm able to get it working with a local test ASP.NET application, but can't seem to find any information on the steps necessary to do this with a Web Role that can be deployed to Azure. The only information that I've found is to handle this scenario using a custom STS and the ACS or just LiveID, but nothing that demonstrates using both together.
Is there currently a limitation with Azure that prevents this? I've read some articles that seem to indicate it isn't currently possible due to the Geneva Framework not being fully implemented on Azure - can anyone confirm?
Thank you very much for any help!
You may find this resource useful - http://code.msdn.microsoft.com/wifwazpassive. It shows how to use ACS in an Azure Webrole. It does use a custom STS, not LiveID, but given that it's using Geneva framework components it should be possible to make it work with LiveID.

Resources