IT Blog

This case took me whole day. It wasn't easy because of Azure service is still evolving. Commands and dependencies between them are changing, but documentation do not. Some websites and blogs steered me on the course where to find the solution, but I have not found final, working version. Here are the links: http://msdn.microsoft.com/en-us/library/azure/dn690120.aspx http://michaelwasham.com/windows-azure-powershell-reference-guide/setting-static-ip-addresses-in-a-virtual-network/ So if you are here, you are looking for how to have VM with static IP or you are struggling with problems with creating VM. First thing you must know is that Azure gives your cloud service virtual IP address (VIP). So, even if you are set local network IP for VM's, then still you are using dynamic VIP. If you will stop your virtual machines, then VIP is freed and during next start you will get different IP. To solve this you need to create static VIP. As Microsoft says, you must consider following: Res...

To get file with images listed, simply run powershell and type: Get-AzureVMImage >c:\azureimages.txt

If you are managing many companies through the powershell as me, it's easy to switch to other consumer by accident. So you can run your connection and in the last step enter password for different company which ends in redirection to another Office365 tenant, not that one you have needed. Also, it's time waste to enter credentials twice everytime you need to logon to different tenant. I propose you to keep your credentials in files encrypted and prepare separate scripts for every tenant. I assume that you are using Active Directory module for powershell and can successfully connect to Office 365 by powershell.  If not, please find instructions in " Office365: How to connect to from Powershell ". 1.Store PS password in an encrypted form: Read-Host -AsSecureString "Enter password"  | ConvertFrom-SecureString | Out-File c:\temp\PasswordCompany1.txt Copy file with password to the place you want. We will refer to it's path in the next step. 2. Prepare powersh...