During many of my Azure Information Protection projects, I have always been met with questions about protected PDF files.
Honestly I do not why, but it seems like some companies are using the quote “AIP doesn’t work with PDF files, so we cannot implement that in our organization”. That is bu*ls**t!
Microsoft and Adobe has been collaborating on this feature for a while now, and it is supported in Azure Information Protection or Microsoft Information Protection as it is called now.
For Windows 10 and previous versions through Windows 7 Service Pack 1 you can use Adobe Acrobat Reader, on iOS or Android you must download the Azure Information Protection app from the store.
Support for previous formats:
The PDF readers in the next table support protected PDF documents that have a .ppdf file name extension and older formats that have a .pdf file name extension. Currently, SharePoint Online and SharePoint on-premises use an older format for PDF documents in IRM-protected libraries.
|Windows 10, through Windows 7 SP1
||Azure Information Protection viewer, Gaaiho Doc, GigaTrust Desktop PDF Client for Adobe, Foxit Reader, Nitro PDF Reader, Nuance Power PDF, RMS sharing app
||Azure Information Protection app, Foxit MobilePDF with RMS, GigaTrust App for Android
||Azure Information Protection app, Foxit MobilePDF with RMS, TITUS Docs
Microsoft Flow, PowerApps and SharePoint are rapidly evolving and gaining ground in companies.
If you are not already familiar with PowerApps, I would definitely recommend taking a look at it. With the latest update to Flow it has become even easier to work with, with conditions (And/Or statements) as the have got a good boost!
Use the new advanced conditioner builder as point and click UI, or dig into JSON codes with the peek code action.
More information can be found on Microsofts Flow blog
Yesterday (8th of February) Microsoft released the Windows 10 Insider Preview Build 18334 (19H1) to Windows Insiders in the Fast ring.
The list of changes, improvements, and fixes for PC are long, and I can’t wait to get the lastest version of Windows Insider Preveiw.
To see the complete list of improvements and current known issues, head over to Microsoft’s blog post.
With Windows 10 version 1809, also known as Windows 10 October 2018 Update you can use biometrics to authenticate to a remote desktop session, as long as Windows Hello for Business are allowed and configured with both Azure Active Directory and Active Directory users.
Windows will automatically prompt you for biometrics when you’re creating a remote desktop session to a etc. Windows 2016 Server if you have logged in to your own computer using Windows Hello for Business.
Do you also use shared PCs in your organization?
Within Build 17713 for Windows 10, you have the availability to use “Fast Sign-in,” which let the users sign in to a shared Windows 10 PC in a flash!
It only takes a few minutes to setup – so why not give it a try?
How to enable Fast Sign-in
- Set up a shared or guest PC with Windows 10
- Set the following policy to enable Fast Sign in (Policy CSP/Authentication/EnableFastFirstSignIn)
- With the policy enabled, sign-in to a shared PC with your account and notice the difference!