Multi-tenant Data for ISVs

This article is contributed. See the original author and article here.

permalink: https://aka.ms/FTAISVmultitenant-data


 


reference links permalink:  https://aka.ms/FTAISVmultitenant-data-resources


 


The very nature of an ISV’s business model is to provide a solution applicable to many customers. These multi-tenant solutions require multi-tenant database services as well. But how do you implement multitenancy in a database securely and at scale? How will I balance performance and cost?


 


In this video we’ll introduce you to the design considerations that impact multi-tenant architectures. We’ll then review some of the core design patterns used to implement multi-tenant solutions. For each pattern, we’ll discuss the pros, cons and tradeoffs you will need to consider when choosing a design pattern. Finally, we’ll review some of the tooling that is frequently used to support multi-tenant solutions.


 


Changes to driver signing for Windows 7, Windows Server 2008 R2, and Windows Server 2008

This article is contributed. See the original author and article here.

Effective June 17, 2021, Microsoft partners should utilize the process below to sign drivers for Windows 7, Windows Server 2008, and Windows Server 2008 R2 through the Partner Center for Windows Hardware.



  1. Remove existing signatures from driver binaries.

  2. Generate new catalog files using INF2CAT.

  3. Sign the security catalog files using the IHV/OEM certificate registered with the Partner Center for Windows Hardware.

  4. Add the driver to your HCK file.

  5. Sign the HCK file using the IHV/OEM certificate registered with the Partner Center for Windows Hardware.

  6. Submit the driver package to the Partner Center for Windows Hardware for signing.

  7. Download the signed driver bundle from the Partner Center for Windows Hardware.


As noted in our post on Changes to driver publication for Windows 7 SP1, Windows Server 2008 R2, and Windows Server 2008, Microsoft will discontinue the publication of drivers to Windows Update for Windows 7 SP1, Windows Server 2008, and Windows Server 2008 R2; however, signed drivers will continue to be made available to ensure optimal driver reliability for Volume Licensing customers who have elected to participate in an Extended Security Update (ESU) program. Windows 7, Windows Server 2008, and Windows Server 2008 R2 driver submissions for the Windows Hardware Compatibility Program (WHCP) will continue to be available through January 2023.


 

Changes to driver publication for Windows 7 SP1, Windows Server 2008 R2, and Windows Server 2008

This article is contributed. See the original author and article here.

On June 17, 2021, Microsoft will discontinue the publication of drivers to Windows Update for Windows 7 SP1, Windows Server 2008, and Windows Server 2008 R2. If your organization utilizes the Extended Security Updates (ESU) program, you will continue to have the ability to deploy drivers to your managed devices using Windows Server Update Services (WSUS_ and other supported methods.


As previously communicated, the SHA-1 Trusted Root Certificate Authority expired for Windows 7 SP1, Windows Server 2008, Windows Server 2008 R2 on May 9, 2021 and is no longer used by Microsoft. Due to the discontinuation and expiration of SHA-1 certificates, partners utilizing the Microsoft Trusted Root Program could publish incompatible SHA-2 signed drivers to unpatched Windows client and Windows Server devices. This, in turn, had the potential to cause degraded functionality or to cause devices to longer boot. This occurs because unpatched systems will have code integrity failures when presented with a SHA-2 signed driver.


To minimize the potential impact of these incompatibilities, Microsoft will discontinue publishing of SHA-2 signed drivers to Windows Update that target Windows 7 SP1, Windows Server 2008, Windows Server 2008 R2 devices on June 17, 2021. While these Windows versions reached the end of support on January 14, 2020, we are making this change to diminish disruptions for users who still remain on these versions of Windows. This includes:



  • Any driver package submitted for multi-targeting for currently supported versions of Windows and Windows Server

  • Any driver package targeting versions of Windows or Windows Server that have reached the end of support.


When this change occurs, a notification will be sent to the submitter and they will need to resubmit the shipping label for publishing after they have removed the unsupported versions.









Note: SHA-1 certificates are expired and are already no longer a publishing option for Windows Update.



Continuation of driver signing


Windows 7, Windows Server 2008, and Windows Server 2008 R2 driver submissions for the Windows Hardware Compatibility Program (WHCP) will continue to be available through January 2023. These submissions will continue to be made available to ensure optimal driver reliability for Volume Licensing customers who have elected to participate in the Extended Security Update (ESU) program.


We’re here to help


To test and certify hardware devices for Windows, we recommend that you utilize the Windows Hardware Certification Kit (Windows HCK) and follow the updated driver signing process for Windows 7, Windows Server 2008 and Windows Server 2008 R2 when submitting a driver package for signing via the Partner Center for Windows Hardware.


For more information on ESUs for Windows 7, see the Windows 7 end of support FAQ or the Window Server 2008 and 2008 R2 end of support FAQ. Partners seeking additional assistance are encouraged to reach out to their Microsoft account representatives.


 

Microsoft Viva Insights | Improve productivity and wellbeing | Demo and tutorial, including set-up

Microsoft Viva Insights | Improve productivity and wellbeing | Demo and tutorial, including set-up

This article is contributed. See the original author and article here.

See how Microsoft Viva Insights delivers data-driven privacy, protected insights, and recommended actions to help individuals and teams improve productivity and wellbeing. Engineering leader, Kamal Janardhan, joins Jeremy Chapman for a deep dive and a view of your options for configuration.


 


Screen Shot 2021-06-17 at 1.52.18 PM.png


 














QUICK LINKS:











Link References:



 


Unfamiliar with Microsoft Mechanics?




 


Keep getting this insider knowledge, join us on social:










Video Transcript:

























































Lesson Learned #177: Is possible to use Private Endpoint with Azure SQL External Tables?

This article is contributed. See the original author and article here.

Today, we had a question from a customer asking if could be possible to connect to the Private Endpoint of Azure SQL DB or Synapse using Azure SQL External Tables.


 


The current answer is not, due to, as outbound connections for Azure SQL External Tables are executing from backend nodes that are outside of any private endpoint addressing space. 


 


In this situation, there is not possible and won’t be available in a near future, as alternative, using Azure SQL Managed Instance that allows to use cross database queries among the database that belongs to the same instance or you could use Linked Server.