Recently I've been building an SPFx app that allows a user to see what groups they manage and allow them to bulk update the membership via CSV. One of the first hurdles was to get all the groups the user is an owner/manager of. This needed to work with all group types:
Whether it be a large group or one that has restricted users, you may need to limit who can send to these mail enabled security groups. In addition, you may even want to enable moderation to allow specific users to approve/deny messages from reaching the members.
The good news is that all this can be done by using AD and Exchange to enable group moderation.
We've recently enforced MFA for admin accounts that connect to Exchange (and other O365 Services). This means that in order to connect via PowerShell we need to install the Exchange Online PowerShell module.
Being able to cast your screen to a device that supports Miracast makes presentations so much easier. However, a recent driver update for Intel Wireless cards seems to set the default scaling of the screen to 80%. This makes the screen have giant black bars around the whole edge of the display and makes the display area much smaller. Luckily, this can be fixed quite easily.
I work in a UK based company and we've recently been using Microsoft Teams more and more, which for the most part has been great. However, whenever someone edits an Excel workbook within the Teams web (or desktop) app, they realise that datetime values are in the US format (MM/DD/YYYY). This seems to happen even if they have previously set the regional settings to UK in SharePoint / Office 365. If you haven't yet set the regional settings for the Office 365 group's SharePoint site, then you should do that first. If you have then you can skip this step.
Whenever I start a new .NET Core project I like to separate out parts of the app into individual projects. Traditionally, I break down a solution like this:
[Solution Name].Data - contains models, migrations and database context classes[Solution Name].Logic - contains services, extensions and mapper profiles[Solution Name].Web - contains all web layer componentsIf you've used SharePoint Online before you've probably come across some of it's limitations. Of course you can store up to 30 million items or file in a SharePoint list but if a list view shows more than 5,000 item then you will probably see a nice error either in the web UI or from console if you use any of the SharePoint tools.
So you have a project that will only run/build using an old Node.js version that you can't upgrade but you also do development using the latest version. What do you do? Only build using your CI pipelines? That could work but would make the development process slow.
I've run into this problem a few times, mainly with SharePoint Framework (SPFx) solutions that only support a particular (old) node version. This is where the Node Version Manager comes in and saves us!
Getting a user's calendar folder permissions in Exchange via PowerShell is pretty straight forward as you can just use the standard :\\Calendar naming convention like below:
Get-MailboxFolderPermission -Identity user@domain:\\Calendar
Every command you type into a PowerShell console is recorded in a single file in the current user's app data directory. This is useful when you need to refer back to a command you entered but it can be security risk if you've entered sensitive data in plain text (like passwords or user data). In those cases try to use secure objects like PSCredential for usernames and passwords.