For more like this, subscribe to the newsletter and get these links and more in your email.
M365 Links:
Be sure to subscribe to my M365 Newsletter for more M365 expertise and news.
Follow these topics: Weekly Links
More Questions about Ediscovery People are too Afraid to Ask
Blatant Hypocrite Ajit Pai Decides To Move Forward With Bogus, Unconstitutional Rulemaking On Section 230
Oregon FBI Tech Tuesday: Cyber Security Awareness Month
Making it personal: The effects of alcohol and substance abuse in the legal community
The Disgruntled Employee and the Damage They Can Do
Why Lawyers Need to Use Multi-Factor Authentication
Launching Today: A Global Directory of Legaltech Products and Resources
TikTok Toe: Tackling Ediscovery for the New Kid on the Social Media Block
Let’s talk about mental health in the workplace
Why You Shouldn’t Believe Everything You See on Social Media
Preventing Employee Burnout Among Remote Workers
How to help an employee with an anxiety disorder
Always Check the Facts Before You Share the Story
And this really brings me back to my point, that we do a poor job of truly understanding science, statistics and cause and effect. We believe that algorithms have all been well-thought out, and produce a “true” result, even when they are trying to predict something as unpredictable as what traffic will look like 20 years from now. We assume social science studies are giving us the “right” answer for how to educate people, or train them for the best outcomes, without considering what we are teaching them about the larger world. We assume that we can tweak one belief, or one thing, without human beings reacting to those changes in unpredictable ways, all the while thinking our one change will cause the reaction we DO predict.
We assume a lot that should never be assumed. We over-simplify a world that actually has more influences than we can possibly account for, and assume that what is really a small statistical difference represents a universal truth.
It doesn’t. There are no simple answers. It takes hard work, hard discussions, and lots of listening to figure out the best way forward. Don’t wait for AI to tell you what to do, it may be missing quite a bit.
As the article mentions, Microsoft does not make it easy to manage SAS tokens in bulk. It’s pretty easy to have a bunch of Azure data blob storage items lying around for years with active SAS tokens that were totally forgotten about.
If you’re using SAS tokens to share data, and it’s good for that, remember to clean up after yourself.
For more like this, subscribe to the newsletter and get these links and more in your email.