Monday, 27 March 2017

Azure Germany in CSP

Azure in Germany was launched in 2016, and if you’ve heard about that, you may already know, that Azure in Germany is different from other Azure regions.
Azure in Germany is an isolated instance of Azure. It doesn’t connected to other Azure regions. Azure Portal URL is different – I recommend to read this article to understand high-level details why Azure in Germany was built this way.
Unlike Azure in China, which is operated by 21Vianet and doesn’t even have an English version of the website, Azure in Germany is operated by Microsoft, but with local specifics:
  1. German Azure regions are isolated from other regions (Europe, US, Asia). The network between these datacenters is isolated and dedicated within Germany.
  2. Support for Azure Germany comes from EU-based support staff. The German data trustee supervises all support that requires platform access.
  3. Customer data remains in Germany under the control of T-Systems International GmbH, a subsidiary of Deutsche Telekom, acting as the German data trustee. Microsoft does not have access to customer data or the datacenters without approval from and supervision by the German data trustee.
  4. Originally these regions were available only for the customers with business address in Germany. Recently it was extended to any customers with business address in EU/EFTA.
  5. Azure Germany is deployed in 2 regions – Germany Central (Frankfurt) and Germany Northeast (Magdeburg, not far from Berlin). Germany Central region is bigger and has more Azure services deployed. Price for Azure services in these two regions is pretty the same, it is a little bit higher than in Global Azure regions in Europe (West Europe, North Europe).
  6. Azure in Germany has its own Azure Portal ( and its own tenants (*
  7. You need to specify that you want to connect to Azure Germany in PowerShell or CLI. For example, this is an example for PowerShell: Login-AzureRmAccount -EnvironmentName AzureGermanCloud
How Azure in Germany is different from CSP perspective:
  1. To be available to sell German Azure to your customers in EU/EFTA, you’ll need to get a separate Partner Center account by completing an additional enrollment. You will use a separate partner tenant to login into Partner Center – Once authorizes, you will be able to create customer accounts in any EU/EFTA country.
  2. Only partners with EU/EFTA business address are allowed to enroll to German Partner Center.
  3. Partner Center capabilities for German partner accounts are limited. Check here for details.
  4. All Azure services will be deployed in Germany (the same for Office 365). You can’t assign your customer a Global Azure subscription from German Partner Center account.
  5. German CSP services are billed in 6 local currencies – EUR, GBP, NOK, SEK, DKK, CHF.
  6. License-based Azure subscriptions (Azure AD, Azure MFA etc.) are not available. Only usage-based Microsoft Azure Germany – CSP.
  7. Not all Azure CSP services are available in Germany. Check here for details.
  8. Despite the fact that Azure Machine Learning is available in Azure Germany, it is not currently available in Azure CSP subscriptions.
  9. KeyVault in Azure Germany is not accessible through Azure Portal, but it is accessible through PowerShell. There isn’t a sovereign Certificate Authority integrated in Azure Germany. You’ll need to create the CSR and then get it signed by CA of choice, and then merge the certificate in KeyVault.
  10. Not all VM sizes are available. Check here for details.
  11. Azure ADs in Global Azure and in Azure Germany are fully isolated from each other. If On-Premise AD of a German customer is already integrated with Global Azure AD (using Azure AD Connect or other tools), you won’t be able to integrate it with German Azure AD before dropping the old integration.
I think that Azure Germany is a great example of a public cloud, that is truly aligned with local regulations. I recommend all EU/EFTA CSP partners to try it.

Friday, 2 December 2016

Microsoft Ignite Australia 2017

Microsoft Ignite. Just who is it for?

Technically speaking, Microsoft Ignite Australia is for techies. We’re talking Developers and IT Pros. It’s also for anyone who works with people who work with technology. But look a little deeper and delegates have so much more in common.

Step by Step Installation of Windows Server 2012

1- Insert the Windows Server 2012 DVD, and once you get the following message press Enter to boot from the setup

2- Wait for a while till the setup loads all necessary files (Depending on your machine, it will take couple of minutes)

Friday, 27 March 2009

Exchange 2010 Installation Requirement

To run Microsoft Exchange Server 2010 Enterprise Edition Beta on x64 platforms, you need:
·        PC―x64 architecture-based computer with Intel processor that supports Intel 64 architecture (formerly known as Intel EM64T) or AMD processor that supports the AMD64 platform
·        Operating system―Microsoft Windows Server 2008 Standard x64 Edition or Enterprise x64 Edition
·        Operating system for installing management tools―The 64-bit editions of Microsoft Windows Vista SP1 or later, or Windows Server 2008. Note: Requirements only for management tools installation.
Additional requirements to run Exchange Server 2010 Beta
·        Memory―Minimum of 4 gigabytes (GB) of RAM per server plus 5 megabytes (MB) of RAM recommended for each mailbox
·        Disk space
o   At least 1.2 GB on the drive used for installation
o   An additional 500 MB of available disk space for each Unified Messaging (UM) language pack that you plan to install
o   200 MB of available disk space on the system drive
·        Drive―DVD-ROM drive, local or network-accessible
·        File format―Disk partitions formatted as NTFS file systems
·        Monitor―Screen resolution 800x600 pixels or higher

Exchange Server 2010 Beta Prerequisites

Wednesday, 25 March 2009

How to Recover an Exchange 2007 Mailbox

To recover a Microsoft Exchange 2007 mailbox, the recovered .edb and .log files need to be attached to the Recovery Storage Group in Exchange and you must use Exchange-supported tools, such as Exmerge.exe, to extract a .pst file.
The procedure you use depends on whether there is an existing mailbox to which you want to recover a previous version or the mailbox no longer exists and you want to recover it.