Office-docs-powershell: EnableSafeLinksForClients or EnableSafeLinksForO365Clients

Created on 12 Dec 2019  Â·  14Comments  Â·  Source: MicrosoftDocs/office-docs-powershell

This is too confusing. -EnableSafeLinksForClients is working for one tenant and -EnableSafeLinksForO365Clients is working for another. Example uses -EnableSafeLinksForClients tells what is it doing but later on the page -EnableSafeLinksForO365Clients is describing the same action. I confirmed on 3 different tenants with same subscriptions.


Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

exchange

All 14 comments

@officedocsbot assign @yogkumgit

Any updates. This is important.
Thanks

Hi @NiteshSharma2K19, thank you for your feedback.

Really this parameter is EnableSafeLinksForClients and I have test in some tenants. Where do you find EnableSafeLinksForO365Clients? Could you let me know what licenses do you have in these tenants?

I'm updating the article.

@dariomws306
-EnableSafeLinksForO365Clients
The EnableSafeLinksForO365Clients parameter specifies whether Safe Links is enabled for Office 365 apps on desktop clients and the web. Valid values are:

$true: Safe Links are enabled for Office 365 apps. This is the default value.

$false: Safe Links are disabled for Office 365 apps.

This is the definition of the cmdlet on this doc. This is explaining the same action which is described in example 1. This is confusion.
We have E5 subscription in all three tenants. Please find the links below for two different tenants, where I tried the same using PowerShell.


It should be EnableSafeLinksForClients, I'm updating the document. I cannot say why you have EnableSafeLinksForO365Clients in one tenant, sorry.

Can you please guide me what can be done then on the tenant where I am getting the error that "A parameter can not be found that matches parameter name 'EnableSafeLinksForClients"?

@chrisda Please merge this PR #4548

Use which ever one is currently available to you: EnableSafeLinksForClients for most people, and EnableSafeLinksForO365Clients if it happens to be available to you. They are functionally the same, and I'm told that eventually EnableSafeLinksForO365Clients will replace EnableSafeLinksForClients, but the change hasn't been implemented everywhere yet.

Thanks @chrisda , for the explanation. So instead of the changes made by @dariomws306 we should include your comment as a note. This should resolve the confusion. Also, we were getting the below error when we did a test for security analysis.

This was there when we have EnableSafeLinksForClients giving False and EnableSafeLinksForO365Clients True.

Thanks again,
Nitesh

@dariomws306 Thank you very much for the contribution and updating the documentation with PR. @NiteshSharma2K19 Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also

Hello @yogkumgit , Can you please also add the Comments suggested by @chrisda . This will help others to understand what is going on with these two Cmdlets. This was confusing to me, even I am working for MS.

@chrisda What do you think? Should we add a note to let readers know that it would be EnableSafeLinksForO365Clients in the future?

I have created a new PR to add this comment. @chrisda please approve it if you are agree.

Thanks!

@NiteshSharma2K19 Hope this update looks ok now. Thanks for your kind feedback. Appreciate.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Archehandoro picture Archehandoro  Â·  4Comments

mrik23 picture mrik23  Â·  5Comments

CallMeByMyName picture CallMeByMyName  Â·  5Comments

tomresing picture tomresing  Â·  5Comments

markgort86 picture markgort86  Â·  4Comments