Tag:"scripting" | Microsoft Community Hub

Deprecation of Remote PowerShell (RPS) Protocol in Security and Compliance PowerShell
Starting July 15, 2023, we will start deprecating the legacy RPS protocol in the Security and Compliance PowerShell module.
The_Exchange_Team
Mar 11, 2025 Place Exchange Team Blog
46KViews
2likes
6Comments
Retirement of RBAC Application Impersonation in Exchange Online
We wanted to announce deprecation plans for ApplicationImpersonation role in Exchange Online.
The_Exchange_Team
Feb 14, 2025 Place Exchange Team Blog
156KViews
7likes
174Comments
Introducing Copilot support for Python in Excel: Advanced Data Analysis Using Natural Language
Copilot in Excel will help you analyze and explore your data in a new way: writing Python code
DavidM
Jan 21, 2025 Place Excel Blog
63KViews
7likes
6Comments
Deprecation of Remote PowerShell in Exchange Online – Re-enabling or Extending RPS support
We wanted to let you know about the next chapter in our retirement of RPS protocol in Exchange Online.
The_Exchange_Team
Jan 20, 2025 Place Exchange Team Blog
154KViews
4likes
52Comments
Announcing Optional Help File Loading in Exchange Online PowerShell
Today, we are announcing updates to the Connect-ExchangeOnline cmdlet used to connect to Exchange Online.
The_Exchange_Team
Jan 17, 2025 Place Exchange Team Blog
5.6KViews
4likes
3Comments
Announcing Client Credential Flow for SMTP AUTH in Exchange Online
We are excited to announce support of Client Credential Flow (CCF) for SMTP AUTH in Exchange Online.
The_Exchange_Team
Dec 11, 2024 Place Exchange Team Blog
25KViews
14likes
17Comments
Introducing PS.MTA-STS: a PowerShell module to enhance mail flow security with MTA-STS
Learn how to use this open-source module to configure and test MTA-STS for your Exchange Online domains in a few steps.
The_Exchange_Team
Nov 06, 2024 Place Exchange Team Blog
16KViews
14likes
9Comments
Reducing Memory Consumption of the Exchange Online PowerShell V3 Module
Tips on how to reduce the memory consumption of the PowerShell V3 module and optimize your scripts for better efficiency.
The_Exchange_Team
Oct 29, 2024 Place Exchange Team Blog
17KViews
11likes
4Comments
Announcing Python in Excel: Combining the power of Python and the flexibility of Excel.
Since its inception, Microsoft Excel has changed how people organize, analyze, and visualize their data, providing a basis for decision-making for the millions of people who use it each day. Today we’re announcing a significant evolution in the analytical capabilities available within Excel by releasing a Public Preview of Python in Excel. Python in Excel makes it possible to natively combine Python and Excel analytics within the same workbook - with no setup required. With Python in Excel, you can type Python directly into a cell, the Python calculations run in the Microsoft Cloud, and your results are returned to the worksheet, including plots and visualizations.
msexcel
Oct 24, 2024 Place Excel Blog
1.4MViews
25likes
160Comments
Amazing discovery about Guid's and how to use them to evenly distribute automation over time
I recently re-discovered something, only this time was equipped to take advantage. I place this post here in the Exchange forum since this is my area of most interest, especially relating to using this discovery. Guid's (ObjectGuid, ObjectId, ExchangeGuid, ArchiveGuid, ExternalDirectoryObjectId, etc.) are system-generated and are made up of hexadecimal characters. The amazing discovery is that the degree to which these things are alphabetically balanced is astonishingly perfect. That is, if you take a random sampling of say 16,000 Guid's, you will most likely find that 1000 of them start with '0', 1000 start with '1', 1000 start with '2', ...through until 1000 start with '9', then 1000 also start with 'a', 1000 start with 'b', and so on up to 1000 start with 'f'. It keeps getting better though! Every next character is again evenly distributed. So for example, of all the Guid's starting with '0', roughly 1/16th of them will have '0' for the 2nd character, 1/16th will have '1' for the 2nd characters, and so on up to 1/16th will have 'f' for their 2nd character. This continues but admittedly becomes less perfect the deeper we go. Also, this amazing phenomenon works best when all the Guid's are coming from the same place, such as the list of Azure AD accounts in your tenant, or the list of ExchangeGuid's for your EXO mailboxes. Where this amazing'ness comes into play that completes my reason for this post? It is for large organizations who need to perform reporting and/or automation against their high volume of users or mailboxes (or other entities that are plentiful and have Guid's). Knowing how perfectly distributed the Guid's are alphabetically, we can program around the clock and always be dealing with a consistent level of load. Think back to EXO PowerShell pre-V2 when everyone's scripts would fail if their organization had more than a few hundred mailboxes. Well in this example, we can spread the 16 hexadecimal characters over the days in the week and each day deal with only 1/16th, or 2/16th's, etc. For example: function getTodaysMailboxes { param ( [Object[]]$Mailboxes ) try { $_guidDay = @{ 'Monday' = '0', '1', '2', '3', '4' 'Tuesday' = '5', '6', '7', '8', '9' 'Wednesday' = 'a', 'b', 'c', 'd', 'e' 'Thursday' = 'f', '0', '1', '2', '3' 'Friday' = '4', '5', '6', '7' 'Saturday' = '8', '9', 'a', 'b' 'Sunday' = 'c', 'd', 'e', 'f' } $_todaysGuids = $_guidDay["$([datetime]::Today.DayOfWeek)"] $Script:TodaysMailboxes = @($Mailboxes | Where-Object { $_todaysGuids -contains $_.Guid.ToString().SubString(0,1) }) writeLog @writeLogParams -Message "Identified $($Script:TodaysMailboxes.Count) mailboxes to process today ($([datetime]::Today.DayOfWeek)'s = (EXO) Guid's starting with: $($_todaysGuids -join ', '))." } catch { throw } } And that example is just for daily script execution. You could instead pick a more frequent schedule, say hourly, with the goal to cover every mailbox in 1 week. There are 168 hours in the week, and there are 256 combinations of the first 2 characters in the Guid's. So, if you spread those 256 combos over those 168 hours, all 168 hours would process 1 combo's worth of Guid's, and then 88 of those hours could process 1 extra combo, covering all 256 combos. It would end up being a tiny amount of work every hour, which should lead to less long-running scripts, less data being pulled in short amounts of time, and less failures all around. I personally for now am making use of the code sample above to run scripts nightly which cover off 4-5/16th's all all my org's mailboxes. Every 1 weeks, all of my mailboxes have been processed twice. This could be for pulling mailbox statistics, or mailbox permissions, AAD sign-ins, all kinds of stuff. To summarize this is one cool and easy way to evenly distribute your scripting work over a set amount of time. I don't think you'll find another property on objects that is so well distributed as Guid's. One more reason to love the Guid.
Solved
JeremyTBradshaw
Jun 28, 2024 Place Exchange
4.1KViews
0likes
2Comments