Always on VPN prompting for action needed - Azure AD Join issue?
Hello! We have Always on VPN implemented for our Windows 10 laptops. Everything was/is working great, until we purchased Microsoft 365. Once devices started to Azure AD Join, it put in an additional user certificate from MS-Organization-Access. Now, anytime a user logs in, instead of automatically connecting as they expect, you will have to go to the VPN connection and you will see "Action Needed." Once you click connect, it brings up a dropdown to select which certificate to use, the options being the one created for AoVPN (email address as the name) and the other being the one created by the azure ad join. Selecting and connecting the proper certificate does not persist between logins. Is there a way to specify which certificate it needs to be pointing at to avoid this issue?More Questions From Customers About SQL Server Transparent Data Encryption – TDE + Azure Key Vault
First published on MSDN on Apr 04, 2017 Recently many customers have been moving from AIX and HPUX to Windows 2016 & SQL Server 2016 running on Azure as these UNIX platforms are no longer mainstream, developed or invested by their vendorsMost of these customers are deploying TDE to protect the Database files and backups.Large Australian Energy Company Modernizes SAP Applications & Moves to Azure Public Cloud
First published on MSDN on Mar 27, 2017 This blog is a technical overview of a project recently completed by a large Australian Energy Company (the Company) over the past 12 months to transform the Company's SAP Solution from an End of Life HPUX/Oracle platform to a modern SQL Server 2016 solution running on the Azure Public Cloud.
