Cmdlets that Use the Global Scope and the Tag Scope
Topic Last Modified: 2013-08-19
In Lync Online, policies can be configured at either the global scope or at the tag scope (or per-user scope). When using the Get-Cs cmdlets, you do not have to specify a scope or identity. If you call one of these cmdlets without any parameters, then all the relevant items will be returned. For example, this command returns information about all your external access policies:
You need to include only the Identity parameter or the Filter parameter if you want to limit the returned data. For example, to return only the global policy, use this command:
Get-CsExternalAccessPolicy -Identity "global"
To return a per-user policy that has the Identity “RedmondAccessPolicy”, use this command:
Get-CsExternalAccessPolicy -Identity "RedmondAccessPolicy"
When referencing a per-user policy, the tag prefix is optional. This syntax, which includes the prefix, is also valid:|
Get-CsExternalAccessPolicy –Identity "tag:RedmondAccessPolicy"
To return all policies except the global policies (that is, all the per-user policies), use this command:
Get-CsExternalAccessPolicy -Filter "tag:*"
The following cmdlets operate against both the global scope and the per-user (tag) scope:
|Despite the name, dial plans are, functionally speaking, policies. The term dial plan is used instead of, for example, dialing policy, in order to preserve the terminology used with previous versions of Lync Server.|