Our team has migrated from Azure Mobile Service to AppService and all works fine, except now we need to swap the APNS cert as it's reaching its expiry date.
According to this article: https://learn.microsoft.com/en-us/azure/app-service-mobile/app-service-mobile-migrating-from-mobile-services it has to be done manually in the file system.
Can someone explain how to do it, using the legacy push? Is it the FTP that I need to use? or maybe something else?
Can someone explain how to do it, using the legacy push?
Currently, the Mobile Apps feature of Azure App Service uses Azure Notification Hubs to send pushes,so we need to configurate the notification for the Appservice. The following is the detail steps:
1.In the azure portal,go to your app service and click [push]
2.Click connect to connect or add a notification hub source to the app
3.Click [Configure push notification services] to configurate push notification
services.
4.Upload the certificate
We also could get more info from the azure tutorials.
After some investigation I happily found an answer to this question and I thought it'd be good for others who don;t want to upgrade to NH to share it.
It's enough to go to App Service Editor -> App_Data and swap the certificate there. And this is really it. No need to go to Notification Hubs.
This isn't a Microsoft's recommened approach but it's safe for applications that are already in production state.
Related
I have been using this MSDN tutorial (Tutorial: Send notifications to Universal Windows Platform apps using Azure Notification Hubs) to test the notification hub. The issue is it is asking me to create an app in Windows Store for which I need to register for Microsoft developer and it seems to be paid service. I'm trying to find an alternative here to get Package SID and Security Key for Windows (WNS) settings to register for an Azure Notification Hub. Please suggest.
The Windows Dev Center requires an account with a one time payment as specified on the Register to be an App Developer page.
Is there any way to debug SharePoint online Remote Event Receiver i.e. provider hosted app without using Azure Service Bus ? I don't have Azure Service bus subscription as my organization doesn't allow to connect code over there.
Assuming it's a provider hosted app...you can debug it like any other web app. For example, I have typically deployed my provider hosted apps to Azure, and then use Visual Studio to debug the Azure web site. I've used it in the past on remote event receivers as well.
It's rather lengthy, but you can look at aspects of such a design here: https://samlman.wordpress.com/2015/02/28/cloudtopia-connecting-o365-apps-azure-and-cortana-part-1/.
You have to enable debugging on the web site - have you tried that? I described a second way to do it here if you want to give it a shot: https://samlman.wordpress.com/2015/02/27/another-cool-way-to-remotely-debug-azure-web-sites/.
I've created an Azure App Service application and pushed it to Azure. Unfortunately, I am unable to find the application key that I should use in my client to create the connection to the service (as seen in the below code ).
MobileService = new MobileServiceClient(
"http://xxxx.azurewebsites.net",
"applicationKeyShouldGoHere");
I've seen a few answers to this question, but all seem to point to authenticating the USER within the client. I want to authenticate the call to the service.
Azure Mobile Services had an application key but I'm unable to find the key for App services. The difficulty is multiplied with the fact that the Azure Portal seems to get modified every couple of months...
Thanks in advance.
The new Mobile App Services doesn't need/use any Key.
You need to use Version 2+ of the Microsoft.WindowsAzure.Mobile package on your client.
The older SDK created the MobileServiceClient like this:
new MobileServiceClient(applicationURL, applicationKey)
The new (Version 2+) like this:
new MobileServiceClient(applicationURL)
So there is no need for a key.
We don't publish Azure App Service in the way as we publish Mobile Services(Actually in new portal, there is no Application Key for Mobile services either).
When publishing Azure App Service, you need to download the publish profile from the portal. Right click the project in VS, and choose Publish.... In the Publish Web wizard,import the publish profile you downloaded. When the wizard completed, the App Service will be published to Azure.
Check web-sites-dotnet-get-started for details.
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.
If you follow Microsoft's instructions here to enable RDP on instances in a Cloud Service, they tell you to create a user and set a password for remote desktop purposes.
As this can quickly become a "shared account", I am wondering how one goes about linking this to a person. The Azure Operation logs do not seem to keep track of who RDP'ed or not, and the Windows Security Event Log obviously has no idea what user was connecting other than the user you created. This make traceability difficult.
While I understand RDP should only be enabled for troubleshooting purposes, I am hoping I missed something simple that would allow Azure Cloud Service users to enable RDP without losing all traceability on who is accessing what instance.
Short Version: How do I know who connected over RDP using the shared RDP Account? Azure logs, infrastructure logs maybe?
Thanks
There have been a few changes since the link you mentioned is published:
You can now enable/disable remote desktop through the portal. You don't have to do it at the time of publishing your cloud service. Using this, you can provision remote desktop connections for individual users in your team instead of relying on one shared RDP connection. To do so, click on CONFIGURE tab for your cloud service and then click on Remote icon and follow the instructions.
The thing you do on portal with remote desktop can also be done programmatically using Service Management API. With the latest Service Management API release, RDP functionality is basically an extension which you can enable/disable on the fly. I wrote a blog post not too long ago describing this functionality: http://gauravmantri.com/2013/05/06/windows-azure-cloud-services-extensions-and-service-management-api-fun-with-remote-desktop/
I haven't actually looked at security event logs so I can't say for sure that it would log this activity but I'm assuming it would.