Can customers run Microsoft Office and Windows 7 Client on virtual machines using Licence Mobility for Software Assurance?

No. Under the Microsoft Product Use Rights (PUR), Office and Windows 7 are not licenced to run on virtual machines. In particular, Microsoft Office is classified in the PUR as “Desktop Applications”, which is not included in Licensing Mobility. More information is available at the site for Microsoft Product Use Rights.

Related questions and answers

  • A brokered connection is defined as one of the following:

    1. An AMQP connection from a client into a Service Bus topic, subscription, queue or event hub.
    2. An HTTP call to receive a message from a Service Bus topic or queue that has a receive timeout value greater than zero. Microsoft charges for the peak number of concurrent brokered connections that exceed the included quantity (1,000 in the standard and premium tier). Peaks are measured on an hourly basis, prorated by dividing by 730 hours in a month and added up over the monthly billing period. The included quantity (1,000 brokered connections per month) is applied at the end of the billing period against the sum of the prorated hourly peaks. Examples:
    3. 5,000 clients connect via a single AMQP connection each and receive commands from a Service Bus topic and send events to queues. If all clients connect for 12 hours every day, you will see the following connection charges (in addition to any other Service Bus charges)—5,000 connections * 12 hours * 30.5 days / 730 = 2,500 brokered connections. After the monthly allowance of 1,000 brokered connections, you would be charged for 1,500 brokered connections.
    4. 5,000 clients receive messages from a Service Bus queue via HTTP, specifying a non-zero timeout. If all devices connect for 12 hours every day, you will see the following connection charges (in addition to any other Service Bus charges)—5,000 HTTP receive connections * 12 hours per day * 30.5 days / 730 hours = 2,500 brokered connections.
  • QnA Maker helps you create a bot that conversationally answers questions covered in your documentation, like an FAQ page. Learn more about how QnA Maker works

  • For new conversational experiences, use Bot Framework SDK V4. Whereas customers found the dialog models in Bot Framework SDK V3 to be too rigid and constraining, Bot Framework SDK V4 is modular and extensible. It provides the foundation for bot templates and solution accelerators. If you already have Bot Framework SDK V3 bots in production, they will continue to work as-is for the foreseeable future. Learn more on the Bot Framework FAQ page

  • The premium tier of Service Bus messaging provides all the messaging features of Azure Service Bus queues and topics with predictable, repeatable performance, higher throughput and improved availability. The premium tier uses a dedicated resource allocation model to provide workload isolation and consistent performance. Because the compute and memory resources in the premium tier are dedicated, there are no per-message transaction charges as in other tiers. All transactions are included in the message unit allocation.

  • Azure does not support persistent MAC addresses, and so software with MAC based license models can't be used for both on-premises to Azure migration or disaster recovery.

  • The premium tier of Service Bus messaging is a flat daily rate per messaging unit purchased. Namespaces created as premium can have 1, 2 or 4 messaging units which will each accrue the given number of messaging unit daily rate charges. Premium namespaces can have the number of purchased messaging units changed at any time, but the daily rate is based on the maximum number of message units assigned to the namespace at any time.