While I understand what Microsoft is trying to do, I would have preferred for them to label the switch “Try Outlook Beta” rather than “Try New Outlook”. End users do not appreciate agile software development and the delivery of partially working software as it ready.

Likely the largest issue is Microsoft taking features of Outlook and breaking them off in to distinct Apps, like Tasks. The ToDo App pales in comparison to the task features in the production version of Outlook. You cannot display them with your calendar at the same time to see your total commitments to work. They are missing access to the start date field. It still exists in the data, it is just not accessible in the To App. Add to that Planner tasks which do not sync or display inside Outlook (unless using the ToDo). It is all a hot mess.

The Outlook for Mac appress to be farther in their process as the “good” version is called “Legacy” and the new is now the production. This new Outlook for Mac now long is connected to exchange tasks and only ToDo. It lacks the basic ability to make a new task from an email.

So after griping, a question. Do you know if Microsoft has posted its backlog publicly? It would be nice to know what they plan to work on even if it is not part of the current sprint.

Microsoft has cnfirmed to me that they have withdrawn the feature to make some changes. They will relaunch expiration date support for all sharing links when they’ve taken care of whatever needs to be done.

It’s gone from our tenant too. I’ll be curious about what MS has to say about this. Hope it comes back working correctly.

The feature has disappeared from my tenant too. Microsoft hasn’t said anything publicily that I can track down, so I assume that they withdrew the feature because it had some problems that they couldn’t easily fix. I have asked the development group to comment. They might or might not say anything.

I have reported the same issue to Microsoft – so far no valid feedback.
As it seems Microsoft has now completely deactivated setting an expiration date for all links.

Thanks for your post. We actually have bad reactions from our users about hidden channels that no more notify when channel is mentioned. Worst, at the moment i am writing, option “hide inactive channels” is no more exist in teams clients general settings…
I agree a tenant level feature would be nice.

You won’t see anything. CAE happens automatically.

I think there are a number of kinks to workout when this feature goes live. We’ve had 10+ years of OneDrive account retention for free and people will have done many strange and wonderful things in that time. We’ll find all those things out as the software starts to work. I do like the policy of emptying OneDrive before someone leaves. It makes perfect sense to handover or delete documents before someone walks out the door.

Based on your observations, I did some specific tests and saw the exact same behaviour:
– “Send” button: No expiry date
– “Copy link” then close window => Expiration date working if you use the copied link

I also tested the combined approach:
– Set an expiration date + Apply
– Copy Link
– Send

Result:
– Expiration date works if you use the copied link (or the link you can copy in Manage Access => Links)
– Expiration date DOES NOT work if you use the link provided in the email sent by Sharepoint

Really hoping that Microsoft fix this and also more clearly display the expiration dates of links (instead of a very tiny “calendar” icon).

It depends on how your workflows function. Here’s the licensing FAQ: https://learn.microsoft.com/en-us/power-platform/admin/power-automate-licensing/faqs Probably worth a chat with your local Microsoft licensing specialist.

Another curious issue that arises is from shared mailboxes where we have added a licence (which includes OneDrive) for a period of time when we need to use the shared mailbox directly (i.e. hosting teams meetings) but then removed the licence later on. Now the unlicensed OneDrive report shows a handful of these shared mailboxes. It will be interesting to see if the OneDrives eventually get deleted – all but one are at 0MB anyways.

I also don’t see this option 🙁

With or without Public Preview..
Any thoughts

Although I understand Microsoft’s point of view and strongly agree with them, the Microsoft-Managed Conditional Access Rules could have done the job. Break-glass accounts are sensitive and their whole purpose is to bypass anything including MFA. This adds a level of risk to these accounts (lost or broken fido2 key, …). Also, can’t seem to understand why Microsoft creates such “standard” things as CA rules, to replace Per-User MFA, they’re adaptive, “universal” in a way that allows Microsoft to push rules to tenant… just to create another specific thing in a dark corner of the room that does the same job but goes over it.

I am having the same problem. I am running: Register-PnPAzureADApp -ApplicationName “PnP PowerShell App” -Tenant {tenant-name}.onmicrosoft.com -Interactive – and am getting the error: Register-PnPAzureADApp: {“error”:{“code”:”Request_BadRequest”,”message”:”A null value was found with the expected type ‘Edm.String[Nullable=False]’. The expected type ‘Edm.String[Nullable=False]’ does not allow null values.”,”innerError”:{“date”:”2024-09-10T00:21:51″,”request-id”:”0d72d114-3c23-41ee-ae44-2eb610ed5d5b”,”client-request-id”:”0d72d114-3c23-41ee-ae44-2eb610ed5d5b”}}}

how would this be setup?

I checked my client today.The Hide Inactive Channels option is there.

In my opinion, 56 upvotes is not “lots of feedback”, while they ignore feedback with hundreds if not over a thousand upvotes. They’re ridiculous.

I made a support ticket with Microsoft because they snuck this change in without any notification to Teams Admins. I was told about this change before it was announced and additionally was told they tried to make a toggle to have the metadata stay, but it caused too many issues than good.

In my opinion, Microsoft is getting lazy. No heads up notice to admins. Developers declaring it’s too hard to add an option. I expect much more from Microsoft.

thanks so much!

Who knows? Microsoft hasn’t said anything about this yet.

Yep. There’s even a note now: https://learn.microsoft.com/graph/api/resources/device?view=graph-rest-beta&WT.mc_id=M365-MVP-9501#properties

Well, it’s true that people who are pleased with an implementation seldom voice an opinion. However, the folks who were not happy complained at length to Microsoft in the feedback forum, Reddit, Microsoft forums, and so on. I hated the implementation myself and heard many other MVPs voice a concern that a problem existed. So Microsoft changed. Maybe you should register a feedback forum request to add a setting to control whether metadata is included when pasting.

Any experience with how this works on the Teams mobile app i.e. changing to a guest account when trying to join a meeting? And if someone invites you to join from that meeting – then you get to bypass the lobby? But if there are other restrictions i.e. video, microphone then you would need to leave the meeting, change hats, and rejoin?

I do like one security aspect since a guest user may have a lower security in their home tenant but as a guest they could be forced into an MFA check.

The problem with the chorus of voices saying they didn’t like it is that it could well have just been a noisy minority. All that was ever visible until now was one side of the argument.
Why would anyone who was OK with the old behaviour even think to seek out those conversations to argue in favour of the (now former) status quo?

If you don’t want Copilot to see sensitive documents, protect the documents with a sensitivity label that blocks access to Microsoft content services. https://practical365.com/block-access-to-content-services/

OK, thanks for quick response! This could be a real big issue in terms of compliance (there might be content that is not for the Gen AI to see – especially automatically).

The metadata included in pasted text was the noise. People just didn’t like it and Microsoft received lots of feedback that including the metadata was unpopular. So they removed it.

Summaries work for local files. They don’t need to be in OneDrive or SharePoint.

Above I read something like “The who/when data was adding more noise than value to user workflow” – I totally disagree.
Where is the noise???

It is really a shame if there is no Group Policies or other good ways to control this feature.

An option might have been a safer way to deploy the change, but it seems like from the comments and user requests that people just didn’t like the metadata…

Any change to existing behaviour should always be implemented as an option.

I disagree that the new behaviour should always have been this way. I would argue that it should be message-only if copying a single message, or even messages from a single user… but when copying a conversation there is no longer any indication of who said what, which means it’s no longer possible to copy/paste into case notes.
The problem with a noisy request like MC878422 is that there’s no easy way to argue in favour of the status quo. Making it an option would have allowed telemetry to give a real picture.

All changes to UI cause some form of annoyance to some people. I have never seen a UI change that was universally welcomed.

FWIW, i have seen angry comment on MS blog that it doesn’t unhide channel and users are missing messages in such channel that was deemed inactive for them as they are not actively opening it.

Microsoft supports MFA resources from non-Entra sources. You’ll have to work the details out with Okta, who are well aware of the situation.

Hiding a channel just removes it from user view. It has nothing to do with notifications. Users can unhide a channel at any time.

I think it’s safe to hide the scheduling mailboxes. I do this with my scheduling mailboxes.

And of course – since there is no Exchange licence – we need to use PowerShell to hide the emails.

I do wonder if hiding the email address or blocking the scheduling user account will impact the Bookings app features?

I don’t think so, but you should test this on a trial tenant.

I used PS 7.4.5 signed into a GA account and everything worked without a problem. Creating the app and consenting to permissions needs at least the Entra ID Application Administrator role and I was unsure about what else might be required, so I fired on all cylinders…

Yes, I’m running Powershell 7.4.5 (also tried with 7.4.4 in a different machine) as Administrator, with a Global Administrator user. I will try with a colleague’s global account, just in the case there is an issue with mine.

Are you signed into PowerShell as an administrator (run as administrator). That might make a difference…

Register-PnPEntraIDAppForInteractiveLogin -ApplicationName “New PnP Interactive” -Tenant [….].onmicrosoft.com -Interactive

but the cmdlet is not registering nothing. Nothing happens beyond the warning. Using PowerShell 7.4.5 and PnP 2.10.0
Just wondering if it is an issue with my workstation.., because Register-PnPEntraIDApp also fails in the same point:

WARNING:
No permissions specified, using default permissions

Well, you can’t delete a OneDrive account if it is covered by a retention policy. If it’s not, then you can remove it at any time or let it go into the archive.

That’s my understanding. Things will be much clearer when the actual code is available.

So if I’m understanding this correctly, if for example you had a Purview retention policy that kept all deleted OneDrive accounts forever, the accounts would be moved to the M365 archive, but they would never be deleted due to the retention policy being honoured and would still be searchable and data could be exported using eDiscovery Content Search?

Cheers

Is there anyway we can delete the OneDrive site while the status on the report is set to “Owner deleted from Entra ID”

The same rules apply. You pay five cents per month per gigabyte for archived drives unless your tenant SharePoint storage quota is not fully used, in which case the unused quota offsets any charge arising from the archived OneDrive accounts. In your example, the 50 GB of unused tenant quota will fully offset the 20 GB of archived OneDrive content.

That’s certainly an option… However, the SDK does has some plus points, such as paging management and automatic renewal of tokens.

Any account that does not satisfy an MFA challenge will be unable to connect to the Azure sites/administrartive tools after the requirement is imposed, so yes – if those accounts need to use the Entra admin center, Azure admin center, Intune admin center, Azure CLI, and Azure PowerShell.

I’ve heard back from the engineers and they have concluded that the current AccountDisabled property will never work reliably due to some of its on-premises roots. They’ve added a work item to their list to introduce a redesigned and reimplemented AccountDisabled property that will work reliably. There’s no timeline for this work to be completed. In the interim, the suggestion is to use a custom attribute.

I’m sorry about your difficulty with Teams and have shared your input with the Teams development group. You can also highlight the issue in the Teams feedback forum: https://feedbackportal.microsoft.com/feedback/forum/ad198462-1c1c-ec11-b6e7-0022481f8472

Likewise.

Teams is exhausting. I am shattered after 5 mins of using it. Just the pop showing the actions available “thumb, heart. similes,” and all the other images I have to process every time my mouse moves over a mouse. These flick on and off as I try to reply or select or read the message, which in the end I cannot. Since I started I have gone from productive to exhausted after coming into the office. I have ADHT.
These Teams and the meetings are cause my head to literally spin, and I have to close my eyes, or go for walk, in order to counteract the effect of Teams. Stupidly, we are in the office, and people still us teams.

The same is true for SharePoint inside a browser ( Office 360) where I cannot find anything. All I get sent are “links” to these XL sheets that can only access with a link. I cannot save it anywhere, or have place to Pin, or even a list of items I need to access all the time. No Shortcuts like we had before that I could put on the Windows Desktop, or pin to the Start or Task bar. I do not know how to find any thing.

Heath effects from Teams and Office 360 have been to date: dizziness, severe visual snow ( aka blindness ), severe fatigue, and a disconnect with my colleagues.

I have been thinking of leaving my current job over it, because Teams is driving me away.

If you don’t log into the administrator account to use the shared mailbox, then it would be OK to access the mailbox from a licensed account. However, in the grand scheme of things, is an Exchange Online Plan 1 license too expensive to assign to the account?

Has this ticket been resolved? We are planning migration in our tenant and readeing this makes us weary.

Once you set the AutoSubscribeNewMembers to false, try removing members and adding them back again to the group. That works for me every time.

FolderBind is an Exchange Online mailbox audit record. It indicates the time when a non-owner accesses a mailbox folder. You could report the problem as a support issue to Microsoft to make sure that it gets recorded. It’s the only way the engineering team will spend any time considering the issue.

A good idea thanks. I tried that and it seemed to be missing. ChatGPT and its friends seemed to hallucinate trying to track down an opperation called FolderBind but it didn’t uncover anthing. I would have thought it would have been a basic audit event to know if someone was adding open calendars in your organisation in the hope of gaining advantage they perhaps shouldn’t have. Thanks

Thanks you so much. It works Tony! I also created and added string variables for NewSkuNames and OldSkuNames. They were also shows an output of System.Object[] but now, it’ all good.

[string]$NewSkuNamesOutput = $NewSkuNames
[string]$OldSkuNamesOutput = $OldSkuNames

I think this is probably because the data shown in the report include several arrays (prefixed with {). Try creating new string variables and assigning the arrays to the strings. I made a change to show how:

[string]$NewLicensesOutput = $NewLicenses
[string]$OldLicensesOutput = $OldLicenses

The strings are then reported… and I think this should work

I’ve done some further checking and it seems like the UserAccountControl attribute just doesn’t exist. ExchangeUserAccountControl does, and UserAccountControl is mentioned in the set of filterable properties for recipient filters, but it seems like it’s really only present when you synchronize user accounts from on-premises environments. At least, that’s my working theory. In any case, neither UserAccountControl nor ExchangeUserAccountControl are the solution for creating a filter that excludes disabled accounts. I’ll go back to the developers to see if they have any bright ideas, but this might take some time to tease out.

To solve your problem, I think you can:

– Use a custom attribute (like the ones you’re already using
– Use one of the filterable properties supported by DDLs. For instance, you could set the StateOrProvince property to be ‘Disabled’ for disabled accounts

These are not great solutions because they require admins to update account properties in and I will bring that feedback to the devs. Sorry about the confusion caused by the text of the article. Things might have changed between the time it was written and now. Microsoft has been making some changes to DDL filters to make them more predictable. This might be a side effect… or not.