Azure App Services is now available in Azure UAE regions and Azure Functions and other new services too!

Microsoft Azure is delivering a broad and extensive range of services, advancing organizations across a variety of areas from 60+ Azure Regions. These services are often considered as a go-to option for applications, running businesses and freeing up time and capabilities, enhancing work, and providing scalability.

There are benefits too with data residency provided from Azure UAE Regions, as data can be kept in the two UAE datacenter regions, in Dubai and Abu Dhabi.

From the day that Microsoft has announced global availability of Azure UAE Regions, Microsoft strived to make this more useful for customers and partners such as the recent availability of M and Mv2 Series Virtual Machines to provide SAP S4/HANA high performance, scalability and security along with the addition of new Azure Services to the UAE Regions recently.

Whatever your Application Modernization strategy, Azure is the platform that you need. You can now run App Services, Functions, Azure Red Hat OpenShift, Azure Files Premium tier and Azure DevTest Labs in UAE regions.

  • Azure App Service: Azure App Service is a fully managed platform for building, deploying, and scaling web apps to enable productivity and innovation. App Service helps for building, deploying, and scaling web apps quickly and easily by supporting APIs .NET, .NET Core, Node.js, Java, Python or PHP, in containers or running on Windows or Linux.
  • Azure Functions: Azure Functions allows developers to act by connecting to data sources or messaging solutions thus making it easy to process and react to events. Developers can leverage Azure Functions to build HTTP-based API endpoints accessible by a wide range of applications, mobile and IoT devices.
  • Azure Red Hat OpenShift: Azure Red Hat OpenShift provides a flexible, self-service deployment of fully managed OpenShift clusters. You can maintain regulatory compliance and focus on your application development, while your master, infrastructure, and application nodes are patched, updated, and monitored by both Microsoft and Red Hat. You have the option to choose your own registry, networking, storage, or CI/CD solutions. Or you can get going immediately using built-in solutions with automated source code management, container and application builds, deployments, scaling, health management, and more.
  • Azure Files Premium Tier:  Azure Files premium tier storage offers high-performance, easily accessible file services, built on solid-state drives (SSD). Premium tier is optimized to deliver consistent performance for IO-intensive workloads that require high-throughput and low latency.
  • Azure DevTest Labs: Azure DevTest Labs make it possible to quickly provision development and test environments, which minimizes waste with quotas and policies. The service allows automated shutdowns to be set to minimize costs. Additionally, Windows and Linux environments can be built.

Microsoft changes some of the Office 365 product names

Microsoft are announcing a product name change only  for some of Microsoft365 products. There are no pricing or feature changes at this time!

The new product names are already into effect since the 21st of April , 2020.  The below table shows the Old & New naming for each modified product:

Old Name New Name
Office 365 Business Essentials Microsoft 365 Business Basic
Office 365 Business Premium Microsoft 365 Business Standard
Microsoft 365 Business Microsoft 365 Business Premium
Office 365 Business Microsoft 365 Apps. For Business
Office 365 ProPlus Microsoft 365 Apps. For Enterprise

However, no changes were done for the below products:

  • Office 365 for Enterprise (E1, E3, E5)
  • Office 365 for Firstline workers (F1)
  • Office 365 for Education (A1, A3, A5)
  • Office 365 for Government (G1, G3, G5)

Linked below are two comparison sheets for both Microsoft 365 and Office 365 showing the availability features/products for each plan for both Commercial & Educational plan

Microsoft SPLA | Changes to the 2017 Partner Pricelist

Microsoft will not be announcing any price changes in January 2017 for SPLA licenses. However, Microsoft Dynamics® 365 released in SPLA on February 1, 2016, will replace the current Dynamics CRM SKUs. Microsoft Dynamics 365 is the next generation of intelligent business applications that enable organizations to grow, evolve, and transform. These applications provide CRM capabilities to help engage customers, empower employees, and reinvent products and business models. Microsoft Dynamics 365 helps customers to accelerate their digital transformation to meet the changing needs of their customers and capture the new business opportunities of tomorrow.

 Changes:

  • Dynamics 365 will include Sales, Customer Services and Team Members SALs.
  • The new SKUs/SALs will appear on the February 1, 2017 SPLA price list and the February SPUR
  • Microsoft Dynamics® 365 released in SPLA on February 1, 2016, will replace the current Dynamics CRM SKUs

The following SKUs will be removed from SPLA in February 2017:

Part Number Description
QHH-00028 DynCRMSrvcPrvdr ALNG LicSAPk MVL SAL
QHH-00089 DynCRMSrvcPrvdr ALNG LicSAPk MVL SAL Bsc
QHH-00090 DynCRMSrvcPrvdr ALNG LicSAPk MVL SAL Essntls

The following SKUs will be added in SPLA in February 2017:

Part Number Description
EMJ-00429 Dyn365ForTeamMembers ALNG LicSAPk MVL SAL
EMT-00565 Dyn365ForCustmrSrvc ALNG LicSAPk MVL SAL
ENJ-00705 Dyn365ForSales ALNG LicSAPk MVL SAL

The following table includes the mapping of the old Dynamics Sku’s (AX & CRM) to the new Dynamics 365 Sku’s:

Existing User License New User License
Pro User SAL Sales User SAL
Pro User SAL Customer Service User SAL
Basic User SAL Sales User SAL
Basic User SAL Customer Service User SAL
Essential User SAL Team Members User SAL

Microsoft | Licensing SharePoint Hosting in SPLA

hosting

As it is known in Microsoft SPLA, SharePoint Server Standard and Enterprise licenses are provided under the Subscriber Access License, which means that each end customer’s internal users who can directly or indirectly access the SharePoint Server would need a license. Service Provider will use the software in this case to provide internal users access to content, information, and applications. Therefore, use of SharePoint Server software to provide content, information, and applications that are limited to internal users must be licensed under SharePoint Server SALs.

SharePoint Hosting – Licensing Based on Processors Used

In contrast and in order to provide SharePoint Server as a Website or Hosted and therefore, allowing an unlimited number of external users to access it, in this case, the licensing scheme would shift from SAL to Processor License. Customer may use the software to provide External Users access to content, information, and applications. Customer may also use the software to provide internal users access to content, information, and applications so long as that same content and information and those same applications are also accessible by External Users.

To run Instances of the server software in the Physical OSE on a Server, you need a license for each physical processor that the Physical OSE uses.

To run Instances of the server software in the Physical OSE on a Server, you need a license for each physical processor that the Physical OSE uses. 

Scenario 1

SharePoint Hosting roles are deployed on 1 physical server with 2 physical processors. Therefore, in this case, SharePoint Hosting would require a total of 2 licenses equal to the number of physical processors.

To run Instances of the server software in Virtual OSEs on a Server, you need a license for each virtual processor that each of those Virtual OSEs uses. If a Virtual OSE uses a fraction of a virtual processor, the fraction counts as a full virtual processor.

Scenario 2

SharePoint Hosting roles are deployed on 1 Virtual Machine with 8 Virtual Cores. This Virtual Machine is created on a Physical Server with 2 physical processors and 4 Cores per Processor. In this case partner would need 8 (Virtual Cores) / 4 (Cores per Processor) = 2 licenses.

Microsoft | Windows Server and System Center Core Licensing Update

server2016

Windows Server 2016 & System Center 2016 will be available in SPLA in October.

Licensing Summary:

  • Per core license model replaces processor license model on October SPUR.
  • Each physical processor needs a minimum of 8 core licenses.
  • Both Windows Server Standard & Datacenter Editions provide support for unlimited Windows Server containers.
  • Windows Server Standard Edition requires all physical cores to be licensed in order to run 1 Windows Hyper-V container (or Virtual Machine).
  • Windows Server Datacenter Edition requires all physical cores to be licensed in order to run unlimited Windows Hyper-V containers (or Virtual Machines).

New Licensing SKU’s:

Part Number Item Name
9EM-00562 WinSvrSTDCore ALNG LicSAPk MVL 2Lic Core
9EA-00039 WinSvrDCCore ALNG LicSAPk MVL 2Lic Core
9EN-00494 SysCtrStdCore ALNG LicSAPk MVL 2Lic Core
9EP-00037 SysCtrDatactrCore ALNG LicSAPk MVL 2Lic
9GA-00006 CISSteStdCore ALNG LicSAPk MVL 2Lic Core
9GS-00495 CISSteDCCore ALNG LicSAPk MVL 2Lic CoreL

Licensing Scenarios:

  • Scenario 1: A physical server with 2 Physical Processors and 4 Cores would require in the new licensing method:

In case of Windows Server Standard:

Part Number Item Name Quantity
9EM-00562 WinSvrSTDCore ALNG LicSAPk MVL 2Lic Core 8

 

In case of Windows Server Datacenter:

Part Number Item Name Quantity
9EA-00039 WinSvrDCCore ALNG LicSAPk MVL 2Lic Core 8

 

  • Scenario 2: A physical server with 2 Physical Processors, 4 Cores and 2 Virtual Machines would require in the new licensing method:

In case of Windows Server Standard:

Part Number Item Name Quantity
9EM-00562 WinSvrSTDCore ALNG LicSAPk MVL 2Lic Core 16

 

In case of Windows Server Datacenter:

Part Number Item Name Quantity
9EA-00039 WinSvrDCCore ALNG LicSAPk MVL 2Lic Core 8
  • Scenario 3: A physical server with 2 Physical Processors and 16 Cores would require in the new licensing method:

In case of Windows Server Standard:

Part Number Item Name Quantity
9EM-00562 WinSvrSTDCore ALNG LicSAPk MVL 2Lic Core 16

In case of Windows Server Datacenter:

Part Number Item Name Quantity
9EA-00039 WinSvrDCCore ALNG LicSAPk MVL 2Lic Core 16

*The total licenses needed is divided by 2 since each reporting SKU covers 2 core licenses

Partners whose Microsoft SPLA Agreement is not yet expired, can still report the Windows Server Per Processor License until the expiry date of their Agreement.

Microsoft | Licensing Update

update

Microsoft released a new licensing update for products that are licensed under the Per Core licensing method such as Microsoft SQL and Microsoft BizTalk. Microsoft discontinued the Core Factor when calculating the licenses required for these products. In the new Services Provider Use Rights, you calculate the number of cores on the physical server or the number of virtual cores on the VM. You just need to report a minimum of 4 cores per VM/physical core. You can find below the explanation from the SPUR Document.

For Products under the Per Core License Model, Customer must choose either licensing by Physical Core on a Server or licensing by Individual Virtual OSE. The terms for each are set forth below.

Server Licenses (per core) – Licensing by Physical Core on a Server
1. Customer may use the server software on a Licensed Server, provided it acquires sufficient Licenses as described below.
2. The number of Licenses required equals the number of Physical Cores on the Licensed Server subject to a minimum of four Licenses per Physical Processor.
3. For enterprise editions, Customer may use any number of Running Instances of the server software on the Licensed Server in the Physical OSE and/or any number of Virtual OSEs.
4. For other editions Customer may use any number of Running Instances of the server software only in the Physical OSE on the Licensed Server.

Server Licenses (per core) – Licensing by Individual Virtual OSE
1. Customer may use any number of Running Instances of the server software in any Virtual OSE on the Licensed Server, provided it acquires sufficient Licenses as described below.
2. The number of Licenses required equals the number of Virtual Cores in the Virtual OSE, subject to a minimum of four License per Virtual OSE.
3. If any Virtual Core is at any time mapped to more than one Hardware Thread, Customer needs a License for each Hardware Thread to which it is mapped.