Azure Logic Apps are a great solution to write workflows of the business processes, and that too without writing any code. As a result, unit tests can not be written because there’s no code to write unit tests against. How do one go around testing a logic app then?
How to Test Azure Logic Apps (17 Feb 2018)
Create a dotnet core Azure Function (06 Jan 2018)
Latest version of Visual Studio Extension Azure Functions and Web tools helps you create pre-compiled C# Azure Functions, and lets you write functions as a C# library. Being a pre-compiled function it has better performance while starting up. Along with that, it lets you use Webjobs attributes for declaring bindings, thus not needing a functions.json file. And, it lets you debug and run azure functions locally.
Blocking all external access and securing Azure Functions (06 Jan 2018)
If you’re developing a solution with micro services architecture with Azure, there are chances you’ve been using Azure Functions to develop a service. For example, If you’re solution can involving sending email alerts. One of the microservices here can be Email Service. This can further be broken down into two micro services. One to enqueue mail message to Azure storage queue. This can be a Http Triggered function. Second one can be a Queue trigerred function that prcesses these messages and actually sends the email, using a third party API.
Changing Drive Letter of an Azure Drive (aka X-drive) (06 Feb 2011)
Data Persitence in Azure VM Role (06 Feb 2011)
Azure VM Role involves creating a base image, uploading it to Azure using csupload, and then creating a servic model in Visual Studio to point to the uploaded base image.
Unable to connect to Azure VM Role for a long time after it is Deployed or Restarted (21 Jan 2011)
I have been really frustrated in waiting for days to log in to my VM Role instance via RDP. I have encountered this issue multiple times. Once a VM Role is deployed or it is restarted, we can not login via RDP for a long period, and it takes a lot of time, sometimes 2-3 (random) days once it is back and allows us to connect via RDP.
Startup Tasks in Azure Virtual Machine (VM ) Role (20 Jan 2011)
Since the release of Windows Azure SDK 1.3 we can now have startup tasks defined in the *ServiceDefinition *file for web/worker roles. However, this is not allowed for a Virtual Machine role. So what to do in case you need to have some tasks/scripts to be run on your VM Role’s startup? For example, your VM Role runs some software applications that require some configuration information that can be available only at run time.
Azure VM Role CSUPLOAD Error 0x80070070 Cannot prepare VHD (05 Jan 2011)
Unexpected Error 0x80070070
Cannot prepare VHD C:\Users\user1\Desktop\baseimage.vhd## Reason: The reason for this error as i discovered was that the disk from where it was uploaded was full. When you use csupload it uses temporary directory for preparing image and by default it uses the location from where you are uploading your base image. So if this disk is full you get this error.
How to enable Remote Desktop for your Windows Azure Roles (01 Dec 2010)
The latest Azure SDK 1.3 makes it possible to login to the VM of your web/worker role instances via Remote desktop. So you are not limited to use VM Role in case you need to establish a RDP connection to your VM.
Active Directory Domain Join of Azure Roles Using Connect (16 Nov 2010)
We already have seen how Windows Azure connect can help us in connecting our windows azure role instances to our local computers in the previous post. We also saw in the use cases/scenarios for azure connect, that we can domain join our windows azure roles with our on-premise Active Directory, and this is possible by using connect plug-in.
Guide to Windows Azure Connect (15 Nov 2010)
Building applications for cloud and hosting them on cloud is one of the great things that happened in recent times. However, you might be having number of existing applications that you wish to migrate to cloud, but you do not want to move your database server to the cloud. Or you want to create a new application and host it in the cloud, but this new application needs to communicate with your existing on-premise applications hosted in your enterprise’s network. Other case might be that your new application that you wish to host in cloud will rely for its authentication on your enterprise’s Active Directory.
HTTP Error Code: 400 Message: No tenant signing key of type X509 certificate is provisioned. (04 Oct 2010)
After the September release if you are configuring your service namespace as per old method you might get following error: