Microsoft Azure Hybrid Benefit for Windows Server Sample Clauses

Microsoft Azure Hybrid Benefit for Windows Server. Refer to Section 8.
AutoNDA by SimpleDocs
Microsoft Azure Hybrid Benefit for Windows Server. Under the Microsoft Azure Hybrid Benefit for Windows Server, Customer may use Windows Server Virtual Machines on Microsoft Azure and pay for the cost of compute only (the “Base Instance”). Customer must indicate that it is using Windows Server under the Azure Hybrid Benefit for Windows Server when creating or configuring a virtual machine on Azure. The Online Services Terms govern use of Windows Server under this benefit. Customer may not concurrently allocate Windows Server Licenses to Azure Hybrid Benefit and assign the same Licenses to its Licensed Servers, except on a one-time basis, for a period not to exceed 180 days, to allow Customer to migrate the same workloads to Azure. On the earlier of completion of migration to Azure or 180 days from the start of migration, Licenses will be deemed “assigned to Azure”. Customer may later reassign Licenses back to its Licensed Servers, provided Licenses remain assigned to Azure for a minimum of 90 days. Except as provided below for Windows Server Datacenter Licenses allocated to Azure Dedicated Host, each Windows Server processor License with SA, and each set of 16 Windows Server core Licenses with SA, entitles Customer to use Windows Server on Microsoft Azure on up to 16 Virtual Cores allocated across two or fewer Azure Base Instances. Each additional set of 8 core Licenses with SA entitles use on up to 8 Virtual Cores on one Base Instance. Customer may use Standard or Datacenter software.
Microsoft Azure Hybrid Benefit for Windows Server. Enrolled Affiliate may use Windows Server Virtual Machines on Microsoft Azure and pay for the cost of compute only (the “Base Instance”). Each Windows Server processor License with SA, and each set of 16 Windows Server core Licenses with SA, entitles Enrolled Affiliate to use Windows Server on Microsoft Azure on up to 16 Virtual Cores allocated across two or fewer Azure Base Instances. Each additional set of 8 core Licenses with SA entitles use on up to 8 Virtual Cores and one Base Instance. Enrolled Affiliate may use Standard or Datacenter. Enrolled Affiliate must indicate that it is using Windows Server under the Azure Hybrid Benefit for Windows Server when creating or configuring a virtual machine on Azure. Under the Microsoft Azure Hybrid Benefit for SQL Server. for each SQL Server License covered with SA (“Qualified License”), Customer may consume the Microsoft Azure Data Services identified in the table below in the indicated ratios. If a customer wishes to use Azure Hybrid Benefit for SQL Server to consume two or more Microsoft Azure Data Services, a separate set of Licenses must be allocated for each service. With Azure Hybrid Benefit for SQL Server, customers will not be charged for the usage of a Microsoft Azure Data Service, but they must still pay for the cost of compute (e.g., the base rate), storage, and back-up, as well as I/O associated with their use of the services (as applicable). Customers must indicate that they are using Managed Instance, Azure Data Factory SQL Server Integration Services, or SQL Server Virtual Machines under Azure Hybrid Benefit for SQL Server when configuring workloads on Azure. Customers may supplement workloads running under Azure Hybrid Benefit for SQL Server with fully metered Azure services.

Related to Microsoft Azure Hybrid Benefit for Windows Server

  • Unbundled Network Terminating Wire (UNTW) 2.8.3.1 UNTW is unshielded twisted copper wiring that is used to extend circuits from an intra-building network cable terminal or from a building entrance terminal to an individual End User’s point of demarcation. It is the final portion of the Loop that in multi-subscriber configurations represents the point at which the network branches out to serve individual subscribers. 2.8.3.2 This element will be provided in MDUs and/or Multi-Tenants Units (MTUs) where either Party owns wiring all the way to the End User’s premises. Neither Party will provide this element in locations where the property owner provides its own wiring to the End User’s premises, where a third party owns the wiring to the End User’s premises.

  • Local Circuit Switching Capability, including Tandem Switching Capability 4.1.3.1 Definition 4.1.3.2 Notwithstanding BellSouth’s general duty to unbundle local circuit switching, BellSouth shall not be required to unbundle local circuit switching for <<customer_name>> when <<customer_name>> serves end-users with four (4) or more voice-grade (DS-0) equivalents or lines in locations served by BellSouth’s local circuit switches, which are in the following MSAs: Atlanta, GA; Miami, FL; Orlando, FL; Ft. Lauderdale, FL; Charlotte-Gastonia-Rock Hill, NC; Greensboro-Winston Salem-High Point, NC; Nashville, TN; and New Orleans, LA, and BellSouth has provided non-discriminatory cost based access to the Enhanced Extended Link (EEL) throughout Density Zone 1 as determined by NECA Tariff No. 4 as in effect on January 1, 1999. 4.1.3.3 In the event that <<customer_name>> orders local circuit switching for a single end user account name at a single physical end user location with four (4) or more 2-wire voice-grade loops from a BellSouth central office in an MSA listed above, BellSouth shall charge <<customer_name>> the market based rate in Exhibit C for use of the local circuit switching functionality for the affected facilities. 4.1.3.4 A featureless port is one that has a line port, switching facilities, and an interoffice port. A featured port is a port that includes all features then capable or a number of then capable features specifically requested by <<customer_name>>. Any features that are not currently then capable but are technically feasible through the switch can be requested through the NBR/BFR process. 4.1.3.5 BellSouth will provide to <<customer_name>> customized routing of calls: (i) to a requested directory assistance services platform; (ii) to an operator services platform pursuant to Section 10 of Attachment 2; (iii) for <<customer_name>>’s PIC’ed toll traffic in a two (2) PIC environment to an alternative OS/DA platform designated by <<customer_name>>. <<customer_name>> customers may use the same dialing arrangements as BellSouth customers. 4.1.3.6 Remote Switching Module functionality is included in Switching Capability. The switching capabilities used will be based on the line side features they support. 4.1.3.7 Switching Capability will also be capable of routing local, intraLATA, interLATA, and calls to international customer’s preferred carrier; call features (e.g. call forwarding) and Centrex capabilities. 4.1.3.8 Where required to do so in order to comply with an effective Commission order, BellSouth will provide to <<customer_name>> purchasing local BellSouth switching and reselling BellSouth local exchange service under Attachment 1, selective routing of calls to a requested directory assistance services platform or operator services platform. <<customer_name>> customers may use the same dialing arrangements as BellSouth customers, but obtain a <<customer_name>> branded service.

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

  • System for Award Management (XXX) Requirement Alongside a signed copy of this Agreement, Grantee will provide Florida Housing with a XXX.xxx proof of registration and Commercial and Government Entity (CAGE) number. Grantee will continue to maintain an active XXX registration with current information at all times during which it has an active award under this Agreement.

  • Programming Phase Schematic Design Phase: 2.2.1.3. Design Development Phase:

  • Availability of Verizon Telecommunications Services 3.1 Verizon will provide a Verizon Telecommunications Service to Z-Tel for resale pursuant to this Attachment where and to the same extent, but only where and to the same extent, that such Verizon Telecommunications Service is provided to Verizon’s Customers. 3.2 Except as otherwise required by Applicable Law, subject to Section 3.1, Verizon shall have the right to add, modify, grandfather, discontinue or withdraw, Verizon Telecommunications Services at any time, without the consent of Z-Tel. 3.3 To the extent required by Applicable Law, the Verizon Telecommunications Services to be provided to Z-Tel for resale pursuant to this Attachment will include a Verizon Telecommunications Service customer-specific contract service arrangement (“CSA”) (such as a customer specific pricing arrangement or individual case based pricing arrangement) that Verizon is providing to a Verizon Customer at the time the CSA is requested by Z-Tel.

  • Unbundled Channelization (Multiplexing) 5.7.1 To the extent NewPhone is purchasing DS1 or DS3 or STS-1 Dedicated Transport pursuant to this Agreement, Unbundled Channelization (UC) provides the optional multiplexing capability that will allow a DS1 (1.544 Mbps) or DS3 (44.736 Mbps) or STS-1 (51.84 Mbps) Network Elements to be multiplexed or channelized at a BellSouth central office. Channelization can be accomplished through the use of a multiplexer or a digital cross-connect system at the discretion of BellSouth. Once UC has been installed, NewPhone may request channel activation on a channelized facility and BellSouth shall connect the requested facilities via COCIs. The COCI must be compatible with the lower capacity facility and ordered with the lower capacity facility. This service is available as defined in NECA 4. 5.7.2 BellSouth shall make available the following channelization systems and interfaces: 5.7.2.1 DS1 Channelization System: channelizes a DS1 signal into a maximum of twenty- four (24)

  • Reporting Total Compensation of Recipient Executives 1. Applicability and what to report. You must report total compensation for each of your five most highly compensated executives for the preceding completed fiscal year, if— i. the total Federal funding authorized to date under this award is $25,000 or more; ii. in the preceding fiscal year, you received— (a) 80 percent or more of your annual gross revenues from Federal procurement contracts (and subcontracts) and Federal financial assistance subject to the Transparency Act, as defined at 2 CFR 170.320 (and subawards); and (b) $25,000,000 or more in annual gross revenues from Federal procurement contracts (and subcontracts) and Federal financial assistance subject to the Transparency Act, as defined at 2 CFR 170.320 (and subawards); and iii. The public does not have access to information about the compensation of the executives through periodic reports filed under section 13(a) or 15(d) of the Securities Exchange Act of 1934 (15 U.S.C. 78m(a), 78o(d)) or section 6104 of the Internal Revenue Code of 1986. (To determine if the public has access to the compensation information, see the U.S. Security and Exchange Commission total compensation filings at xxxx://xxx.xxx.xxx/answers/execomp.htm.) 2. Where and when to report. You must report executive total compensation described in paragraph A.1. of this award term: i. As part of your registration profile at xxxxx://xxx.xxx.gov. ii. By the end of the month following the month in which this award is made, and annually thereafter.

  • Reporting of Total Compensation of Subrecipient Executives 1. Applicability and what to report. Unless you are exempt as provided in paragraph d. of this award term, for each first-tier subrecipient under this award, you shall report the names and total compensation of each of the subrecipient's five most highly compensated executives for the subrecipient's preceding completed fiscal year, if-- i. in the subrecipient's preceding fiscal year, the subrecipient received-- (A) 80 percent or more of its annual gross revenues from Federal procurement contracts (and subcontracts) and Federal financial assistance subject to the Transparency Act, as defined at 2 CFR 170.320 (and subawards); and (B) $25,000,000 or more in annual gross revenues from Federal procurement contracts (and subcontracts), and Federal financial assistance subject to the Transparency Act (and subawards); and ii. The public does not have access to information about the compensation of the executives through periodic reports filed under section 13(a) or 15(d) of the Securities Exchange Act of 1934 (15 U.S.C. 78m(a), 78o(d)) or section 6104 of the Internal Revenue Code of 1986. (To determine if the public has access to the compensation information, see the U.S. Security and Exchange Commission total compensation filings at xxxx://xxx.xxx.xxx/answers/execomp.htm.) 2. Where and when to report. You must report subrecipient executive total compensation described in paragraph c.1. of this award term: i. To the recipient. ii. By the end of the month following the month during which you make the subaward. For example, if a subaward is obligated on any date during the month of October of a given year (i.e., between October 1 and 31), you must report any required compensation information of the subrecipient by November 30 of that year.

  • Supplier Diversity Seller shall comply with Xxxxx’s Supplier Diversity Program in accordance with Appendix V.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!