Now that you deploy Cloudyn (see the other article), we will connect our AWS environment to have only one interface, to manage cost for all our cloud provider subscription.
Be careful, from June, this interface will not be free anymore for AWS. It’ll cost you 1% of your annual subscription consumption.
Some months ago, Microsoft acquires the Cloudyn company. This company developed an interface to manage your cost and to have billing information, for one or multiple subscription, on one console. They support some other cloud service provider like AWS and Google Cloud, it’s why it’s very interesting.
For Azure, it’s free of charge to use this software. You can connect your EA, CSP or other subscription.
For AWS, it’s free until June, after it will cost 1% of your revenue (on AWS or Google Cloud).
After seeing on how to start with Intune in the new Azure Portal, we will see how to enroll devices (iOS, Android & Windows 10) and how to deploy applications on them.
With the new Azure portal launched some months ago now, Microsoft is trying to move all management console in this new portal, and it’s the case with Microsoft Intune.
To manage your Intune subscription now, you need to pass through the Azure Portal.
To remember, Intune is a service to manage the mobility of your IT environment (mobile phone, laptop, etc.).
I’ll now explain to you how to start with this new interface.
To start, be sure to have an Intune subscription associated with your account.
Here is the second article of 2 for the Azure Site Recovery implementation with ARM:
Now that the Azure infrastructure is ready, we will go to step 2 to replicate VMs/Applications. Choose from where you want to replicate VMs (On-Prem for me) and to which the Hyper-V site that you created in the first article.
Today we will see how to implement a DRP solution, with Azure Site Recovery. I’ll deploy this solution, based on the ARM. ASR can be used to migrate your VMs to Azure, from VMWare to Azure, etc.
In my DRP plan, the service that I defined as critical for my business is a website. I’ll replicate this VM on Azure, with ASR. You can do the same work with a multi-tier application.
In my architecture, I have a VPN S2S to Azure. Attached to this network who is connected to the VPN, I have a second domain controller, who is acting as DNS.
I recently looking for Azure Automation, from top to bottom. It’s why, in the next 2 articles, we will see how to use this tool, from A to Z:
Today, we will see how to migrate your On-Premises scripts, to Azure Automation.
I recently looking for Azure Automation, from top to bottom. It’s why, in the next 2 articles, we will see how to use this tool, from A to Z:
Start with the first article.
On 28th of September, Microsoft has released the Virtual Network peering, in GA.
This new functionality gives you the opportunity to connect 2 Virtual Network in Azure between them, by using the network of the Azure Datacenter. Bye bye VPN S2S between virtual network 🙂
A major force of infrastructure today is the possibility to use CI/CD. Understand, Continuous Integration and Continuous Deployment.
To resume, these technologies, give the possibility to your developers to create/modify their codes, send them to GitHub for example, build it with Visual Studio Team Services (VSTS), save it on you registry (Azure Container Registry for me), manage the versioning, always with VSTS, send it to your Docker Swarm cluster as container et to finish, access it through a simple web interface.
