Announcement by Microsoft that they had removed the 16-character limit for passwords in Azure Active Directory had been coming for a while. It takes time for Microsoft to deploy such a fundamental change across all the places in their cloud systems where passwords can be changed. The first leaks that something was happening came in late April when people noticed that the user interface in components like the Azure AD portal and Office 365 Admin Center offered administrators the chance to set 256-character passwords.
The new password limit is also mentioned in the Microsoft 365 User Management blog for April 2019 (posted on 7 May). You can’t say that Microsoft didn’t give us hints that this was coming. Continue reading
Microsoft have announced that Azure Site Recovery (ASR) is now built into the virtual machine experience so that you can setup replication in one click for your Azure virtual machines. Combined with ASR’s one-click failover capabilities, its simpler than ever before to setup replication and test a disaster recovery scenario.
Using the one-click replication feature, now in public preview, is very simple. Just browse to your VM, select Disaster recovery, select the target region of your choice, review the settings and click Enable replication. That’s it – disaster recovery for your VM is configured. The target resource group, availability set, virtual network and storage accounts are auto-created based on your source VM configuration. You also have the flexibility to pick custom target settings. You can refer to the animation below for the flow.
If you have applications running on Azure IaaS virtual machines, your applications still have to meet compliance requirements. While the Azure platform already has built-in protection for localized hardware failures, you still need to safeguard your applications from major incidents. This includes catastrophic events such as hurricanes and earthquakes, or software glitches causing application downtime. Using Azure Site Recovery, you can have peace of mind knowing your business-critical applications running on Azure VMs are covered and without the expense of secondary infrastructure. Disaster recovery between Azure regions is available in all Azure regions where ASR is available.
In this example, you run a script to deploy a virtual machine to Azure Stack Development Kit using a Resource Manager template. Before proceeding, ensure you have configured PowerShell
The VHD used in this example template is WindowsServer-2012-R2-Datacenter.
- Go to http://aka.ms/AzureStackGitHub, search for the 101-simple-windows-vm template, and save it to the following location: c:\templates\azuredeploy-101-simple-windows-vm.json.
- In PowerShell, run the following deployment script. Replace username and password with your username and password. On subsequent uses, increment the value for the $myNum parameter to prevent overwriting your deployment.
$myNum = "001"
$RGName = "myRG$myNum"
$myLocation = "local"
New-AzureRmResourceGroup -Name $RGName -Location $myLocation
-Name myDeployment$myNum `
-ResourceGroupName $RGName `
-TemplateFile c:\templates\azuredeploy-101-simple-windows-vm.json `
-NewStorageAccountName mystorage$myNum `
-DnsNameForPublicIP mydns$myNum `
-AdminUsername <username> `
-AdminPassword ("<password>" | ConvertTo-SecureString -AsPlainText -Force) `
-VmName myVM$myNum `
- Open the Azure Stack portal, click Browse, click Virtual machines, and look for your new virtual machine (myDeployment001).
Azure Storage Tables is one of the four Microsoft Azure Storage abstractions available (Blobs, Queues and Azure Files are the other ones) at the time that this blog was written. It is basically a way to store data in a structured way on a non relational database system (meaning, not an RDBMS system).
Since up to today there are no official cmdlets to support entity/row management inside the tables from Azure PowerShell module, I decided to create this simple module to help IT Pros to leverage this service without having knowledge of .NET framework through some simple cmdlets as follows:
||Adds a row/entity to a specified table
||Gets an Azure Storage or Azure Cosmos DB table
||Returns all rows/entities from a storage table – no filtering
||Returns one or more rows/entities based on Partition Key
||Returns one or more rows/entities based on a specified column and its value (equal comparison operation)
||Returns rows/entities from a table based on customer filtering
||Updates a specified table row/entity
||Removes a specified table row