Відео

Great observations. Annoying that it tries every gMSA as you say!

My pleasure my friend!

Wow, thanks! And I had to check out Dinosaur Jr. Somehow I'd never heard of them. I do see the resemblance. 😂

Wow, I feel for you and can certainly empathise. As for advice - it's so difficult. Does your child have a diagnosis? No two people are the same, diagnosis or not, and we have found that we just have to take it a day at a tie.

Oh, strange. There are several reasons why a QR code might not scan properly. Here are some common issues: Poor Lighting: If the area is too dark or too bright, the camera might struggle to read the QR code. Blurry or Damaged Code: If the QR code is blurry, smudged, or damaged, it can be difficult for the scanner to read it. Incorrect Contrast: QR codes need a good contrast between the code and the background. If the colours are too similar, the scanner might not detect it. Size and Distance: If the QR code is too small or if you're holding the camera too close or too far away, it might not scan. Dirty Camera Lens: A dirty or smudged camera lens can prevent the scanner from reading the QR code properly. Obstructions: Ensure there are no obstructions covering any part of the QR code. Software Issues: Sometimes, the issue might be with the scanning app or the device's software. Updating the app or the device's operating system can help.

Really glad I could help.

You are most kind. Thank you!

Mac is definitely worth the money!

Thank you so much. The actual best tip I can give is to keep it simple, and think about Defence in Depth with Entra and Purview. Defender alone is not enough

Thank you. I will consider looking at those. MD102 is in my area of expertise. The AZ ones not so much - but I may give them a go and learn as I go..

I love that. Thank you so much for the kind words.

Do you mean Encrypted files? Detecting encrypted files with Microsoft Purview Data Loss Prevention (DLP) for endpoints can be challenging, as DLP policies typically do not decrypt files to inspect their contents1. However, there are strategies you can use to manage and mitigate the risks associated with encrypted files: Policy Configuration: Ensure your DLP policies are configured to detect and respond to the presence of encrypted files. While the content cannot be inspected, the fact that a file is encrypted can trigger a policy action. File Metadata: Use metadata and file properties to identify encrypted files. This can include file extensions commonly associated with encryption or specific attributes that indicate encryption. Endpoint DLP: Implement Endpoint DLP to monitor and control the transfer of encrypted files across devices and applications. This can help prevent unauthorised sharing or exfiltration of sensitive data. User Education: Educate users about the risks of encrypting files and the importance of following organisational policies for data protection. This can help reduce the likelihood of users encrypting files inappropriately. Advanced Classification: Utilise advanced classification capabilities in Microsoft Purview, such as trainable classifiers, to detect patterns and behaviours associated with the use of encryption tools. By combining these strategies, you can enhance your ability to detect and manage encrypted files within your organisation.

You are most welcome. Thank you for the very kind words.

Try this - admin.microsoft.com/#/Settings/Services

I have that same feeling and I still have not been able to bring myself to call MS Support. Do let me know if you get any success with them.

That is very strange. learn.microsoft.com is my go to usually. I did quickly ask Copilot about this. Here is what it suggested... There are a few reasons why your eDiscovery hold might be toggling off randomly in Microsoft Purview: Policy Conflicts: If there are multiple hold policies applied to the same data source, conflicts can arise, causing one policy to override another. Manual Changes: Someone with the necessary permissions might be manually turning off the hold. System Updates: Updates or changes to the Purview system or related services can sometimes cause temporary disruptions in hold policies2. Configuration Issues: Incorrect or incomplete configuration of the hold policy can lead to it not being applied consistently1. Data Source Changes: Changes to the data sources, such as moving data to a different location or deleting data, can affect the hold status2. To troubleshoot this issue, you can: Review Hold Policies: Check the hold policies to ensure there are no conflicts or manual changes. Audit Logs: Look at the audit logs to see if there are any records of the hold being turned off manually. Check System Status: Verify if there have been any recent updates or maintenance activities that might have affected the hold policies. Reconfigure Policies: Ensure that the hold policies are correctly configured and applied to the appropriate data sources. If the issue persists, you might want to contact Microsoft support for further assistance

How long did you wait for it to take effect? It can take some time.

Thank you so much for the kind words. Congrats on the exam pass!!

Thank you. Hope you get/got on OK with the exam

Think I just answered your same query in another comment. Two weeks eh. That's way too long. I would suggest checking for policy conflicts first. If there are none, perhaps log a ticket with MS Support.

This may help a little.

Thanks for the feedback.

I don't consider any one setting that impactful. My philosophy is very much grounded in the principles of Defence in Depth - across all Security, Compliance, and Identity solutions such as the Defender suite, Entra, and Purview.

You are most welcome!

You are most welcome. Information Protection broadly refers to Sensitivity Labels for Encryption, content marking etc. Information Barriers on the other hand are designed to create segments within a tenant based on groups of users. For example, you might want to prohibit the Marketing Team from communicating with the R&D team, or prevent users within certain locations communicating. Information Barriers will achieve this.

You are most welcome. And yes, I am a JD superfan! Amazing banc. Love New Order too

Hmm, frustrating. If trainable classifiers not applying retention labels as expected, here are some potential issues and solutions to consider: Training Quality: Ensure that the classifiers are well-trained with a sufficient number of positive and negative samples. Microsoft recommends at least 50 positive samples and 150 negative samples. Policy Configuration: Double-check the configuration of your retention label policies. Ensure that the conditions for applying the labels are correctly set up and that the classifiers are included in these conditions. Simulation Mode: If you are using simulation mode, note that it might not work for content classified using machine learning trainable classifiers. Ensure you are testing in a live environment. Licensing and Permissions: Verify that you have the appropriate Microsoft 365 licensing (E3 or E5) and that the necessary permissions are assigned to the users managing the classifiers and retention policies. Content Matching: Ensure that the content you are testing actually matches the criteria defined by the classifiers. Sometimes, the issue might be with the content not being a close enough match to the training samples. Service Updates: Occasionally, service updates or temporary issues with Microsoft Purview can affect the functionality. Check the Microsoft 365 Service Health Dashboard for any ongoing issues. If you've checked all these aspects and the problem persists, it might be helpful to contact Microsoft support for more detailed troubleshooting.

Hi, thanks for the recommendation. I will see what I can do.

Not specifically no, but it should be fairly straightforward to do this. Is it something you have tried and had issues with?

@@peterrisingM365 Yes tried it but no succes as you say it should be strait foward but does not seem to work. Maybe I'm not geting somthing

@@rogermix101 Hmm, maybe I need to do a video on this. Might have a play.

I was really very impressed with it!