You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Skype for Business Server gives users the opportunity to share a wealth of presence information with other people: they can publish a photograph of themselves; they can provide detailed location information; they can have presence information automatically made available to everyone in the organization (as opposed to having this information available only to people on their Contacts list).
27
-
28
-
Some users will welcome the opportunity to make this information available to their colleagues; other users might be more reluctant to share this data.
29
-
(For example, many people might be hesitant about having their photo included in their presence data.) As a general rule, users have control over what information they will (or will not) share; for example, users can select or clear a check box in order to control whether or not their location information is shared with others.
30
-
In addition, the privacy configuration cmdlets enable administrators to manage privacy settings for their users.
31
-
In some cases, administrators can enable or disable settings; for example, if the property AutoInitiateContacts is set to True, then team members will automatically be added to each user's Contacts list; if set to False, team members will not be automatically be added to each user's Contacts list.
32
-
33
-
In other cases, administrators can configure the default values in Skype for Business while still giving users the right to change these values.
34
-
For example, by default location data is published for users, although users do have the right to stop location publication.
35
-
By setting the PublishLocationDataByDefault property to False, administrators can change this behavior: in that case, location data will not be published by default, although users will still have the right to publish this data if they choose.
36
-
37
28
Privacy configuration settings can be applied at the global scope, the site scope, and at the service scope (albeit only for the User Server service).
38
-
The \`Set-CsPrivacyConfiguration\` cmdlet enables you to modify any of the privacy configuration settings currently in use in your organization.
29
+
The Set-CsPrivacyConfiguration cmdlet enables you to modify any of the privacy configuration settings currently in use in your organization.
39
30
40
31
## EXAMPLES
41
32
@@ -76,15 +67,15 @@ The filtered collection is then piped to the \`Set-CsPrivacyConfiguration\` cmdl
76
67
Unique identifier for the privacy configuration settings to be modified.
77
68
To modify the global settings, use this syntax:
78
69
79
-
\`-Identity global\`
70
+
-Identity global
80
71
81
72
To modify settings configured at the site scope, use syntax similar to this:
82
73
83
-
\`-Identity site:Redmond\`
74
+
-Identity site:Redmond
84
75
85
76
To modify settings at the service level, use syntax like this:
86
77
87
-
\`-Identity service:Redmond-UserServices-1\`
78
+
-Identity service:Redmond-UserServices-1
88
79
89
80
Note that privacy settings can only be applied to the User Server service.
90
81
An error will occur if you try to apply these settings to any other service.
@@ -234,13 +225,13 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
0 commit comments