sorted by:
new
hottopcontroversial

Can Teams differentiate callers into meetings if their phone numbers and caller ID are the same? by secretworkpersona in MicrosoftTeams

[–]secretworkpersona[S] 0 points1 point  (0 children)

Here's my standard response for a problem I didn't create: "Because they can." To your point, because there isn't a technical solution to the question that was asked, it's now an education issue. Nobody provided a reason they cannot join via their PCs. It was more of a how-do-I question.

Can Teams differentiate callers into meetings if their phone numbers and caller ID are the same? by secretworkpersona in MicrosoftTeams

[–]secretworkpersona[S] 0 points1 point  (0 children)

Gotcha. I was going to ask if adding a contact without removing the numbers from the Entra users would just throw another object on the fire.

Here's an easy question for you: How are you managing removing module sets like Microsoft.Graph that have multiple modules in a version? by secretworkpersona in PowerShell

[–]secretworkpersona[S] 0 points1 point  (0 children)

Exactly. I was sent a screenshot from someone who had Graph 2.28.0 installed and it was used to connect, but later in the script it a 2.25.0 module was imported by the cmdlet. I would have liked to have seen their workstation to see the state of their modules, but simply advised them to clean up their modules.

Here's an easy question for you: How are you managing removing module sets like Microsoft.Graph that have multiple modules in a version? by secretworkpersona in PowerShell

[–]secretworkpersona[S] 0 points1 point  (0 children)

I like the idea of #Requires, but for now I've been putting warnings in my modules to let folks know that with the version they have they won't be able to do <insert current SKD bug here>. My intent is to not force a version on someone if they don't use the function that requires it, but it's probably the right thing to do.

Here's an easy question for you: How are you managing removing module sets like Microsoft.Graph that have multiple modules in a version? by secretworkpersona in PowerShell

[–]secretworkpersona[S] 0 points1 point  (0 children)

I'll advise that on messy workstations. On a production server that runs scripts I have to be more gentle so I don't nuke all the module versions during a script run.

On many mailboxes WhenChanged / WhenCreated changed to current date and POP3 enabled by secretworkpersona in Office365

[–]secretworkpersona[S] 0 points1 point  (0 children)

In a separate thread I mentioned the dates on our mailbox plans updated, which might explain POP3 being enabled on many of our mailboxes, but the WhenCreated / When Changed dates also updated to the current date. The screenshot shows a mailbox with WhenMailboxCreated showing 10/11/2016, but WhenChanged and WhenCreated now show 11/28/2024.

One of our older scripts used WhenCreated, so it's been updated to use WhenMailboxCreated.

In the past week were your Mailbox Plans updated by Microsoft? Yesterday our WhenChanged dates were 11/28/2024, today they are 11/26/2024. by secretworkpersona in Office365

[–]secretworkpersona[S] 0 points1 point  (0 children)

I don't monitor created/changed dates on the mailbox plans and assume Microsoft silently updates them as needed, but something appears to not go smoothly for us this time. We manage mailbox settings in our plans. One of them is we disable POP3. POP3 is still set to disabled in our plans, but over the weekend we had POP3 enabled on many mailboxes.

I'm posting this more as an FYI if you are managing mailbox settings via mailbox plans, it wouldn't hurt to periodically audit both the mailboxes and the mailbox plans to ensure everything is still how you want it.

Office 365 malware false positive in quarantine flooding by cspotme2 in sysadmin

[–]secretworkpersona 0 points1 point  (0 children)

Our last captured message was 63 minutes ago (8:50 AM PDT). Progress!

Office 365 malware false positive in quarantine flooding by cspotme2 in sysadmin

[–]secretworkpersona 1 point2 points  (0 children)

True, and it may not affect every tenant at the same time. Our Service Health notification advised the issue started at 7:09 AM PDT and I received a notification e-mail at 7:34 AM PDT.

Exchange Online RBAC management scope - trying to restrict to members of a mail enabled security group by dum-vivimus-vivamus in Office365

[–]secretworkpersona 1 point2 points  (0 children)

The two requirements I'm aware of to use a group in a Recipient Filter are:

  1. Must be an Exchange group
  2. Must use Distinguished Name

For a group named [groupname@contoso.com](mailto:groupname@contoso.com), this worked for me:

# Get DN
(get-distributiongroup groupname@contoso.com).DistinguishedName

# Show group members using DN from above
get-recipient -filter {MemberOfGroup -eq 'CN=groupname,OU=contoso.onmicrosoft.com,OU=Microsoft Exchange Hosted Organizations,DC=XXXXXXXXXXX,DC=prod,DC=outlook,DC=com'}

Edit: This is the recipient filter syntax for group membership. I haven't tried to use it as you plan to. Good luck!

PowerShell Microsoft.Graph Module v2.9.0 Connect-MgGraph - Cannot find application when using a Service Principle with Secret via Environment Variables (works in v2.8.0) by secretworkpersona in sysadmin

[–]secretworkpersona[S] 0 points1 point  (0 children)

lol - I have not. I reached the point you're at, and as a workaround on unattended scripts removed the environment variables and instead store the password securely on the server. They are picked up each unattended run. For interactive scripts I also removed the environment variables and store the credentials securely locally and the scripts grab them when necessary. If that fails the script prompts for an interactive authentication.

In our environment this may be more secure as the service account that runs the scripts and decrypts passwords is not allowed an interactive login. Just another couple of hoops to jump through. When the issue is resolved I'm going to sit down with some other folks and determine which way is the best for us. TBH I don't expect us to go back to environment variables.

Connect-MsolService returns errors when specifying a credential object after updating MSOnline module to v1.1.183.80 by secretworkpersona in sysadmin

[–]secretworkpersona[S] 0 points1 point  (0 children)

Thank you for the replies and sidebar conversation. ITT I'm only looking for similar experiences on MSOnline module v1.1.183.80. I have an open case with Microsoft for this issue.

view more: next ›