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
The EventType parameter filters the report by the event type. Valid values are:
148
148
149
-
Email phishing EventTypes:
150
-
151
-
- Advanced phish filter (Indicates a message caught by the machine learning model.)
152
-
- Anti-spoof: Intra-org (Indicates an internal message caught by anti-phish spoof protection.)
153
-
- Anti-spoof: external domain (Indicates an external message caught by anti-phish spoof protection.)
154
-
- ATP-generated URL reputation\* (Indicates a message with a known malicious URL caught Defender for Office 365.)
155
-
- Domain impersonation\* (Indicates a message impersonating a domain protected by an anti-phish policy.)
156
-
- Brand impersonation (Indicates a message caught by phish filters as impersonating a known brand.)
157
-
- EOP URL Reputation (Indicates a message with a known malicious URL caught by EOP.)
158
-
- General phish filter (Indicates a message caught by basic phish protection.)
159
-
- Malicious URL reputation (Indicates a message with a known malicious URL caught by phish filters.)
160
-
- Phish ZAP (Indicates a phish or spam message detected and auto-purged after delivery.)
161
-
- User impersonation\* (Indicates a message impersonating a user protected by an anti-phish policy.)
162
-
163
-
Email malware EventTypes:
164
-
165
-
- Anti-malware engine\* (Indicates a message caught by the anti-malware engine.)
166
-
- Anti-malware policy file type block (Indicates when the Common Attachment Types filter blocks a file.)
167
-
- ATP-generated file reputation\* (Indicates a message with a known malicious file blocked Defender for Office 365.)
168
-
- ATP Safe Attachments\* (Indicates a message with a malicious attachment blocked Defender for Office 365.)
169
-
- ATP Safe Links\* (Indicates when a malicious link is blocked Defender for Office 365.)
170
-
- File Detonation\* (Indicates a message with a malicious attachment blocked by the detonation service.)
171
-
- Malware ZAP (Indicates a message with malware detected and auto-purged after delivery.)
172
-
- Office 365 file reputation (Indicates a message with a known malicious file blocked.)
173
-
174
-
Content malware EventTypes:
175
-
176
-
- AtpDocumentMalware\* (Indicates malicious content detected by Safe Attachments.)
177
-
- AvDocumentMalware (Indicates malware found by the anti-malware engine. Reporting requires Defender for Office 365 or E5.)
178
-
179
-
\* Requires Defender for Office 365 (included in Microsoft 365 E5 or in an add-in subscription).
149
+
- Advanced filter
150
+
- Anti-malware engine
151
+
- Campaign
152
+
- File Detonation
153
+
- File Reputation
154
+
- File detonation reputation
155
+
- Fingerprint matching
156
+
- General filter
157
+
- Impersonation brand
158
+
- Impersonation domain
159
+
- Impersonation user
160
+
- Message passed
161
+
- Mixed analysis detection
162
+
- Spoof DMARC
163
+
- Spoof external domain
164
+
- Spoof intra-org
165
+
- URL detonation
166
+
- URL detonation reputation
167
+
- URL malicious reputation
168
+
169
+
**Note**: Some values values correspond to features that are only available in Defender for Office 365 (plan 1 and plan 2 or plan 2 only).
180
170
181
171
You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
This example creates migration package containers in Azure storage using the supplied account credentials, uploads the package files into them, snapshots the files and lastly returns the connection strings to a PowerShell variable.
An EncryptionParameters object. See [New-SPOMigrationEncryptionParameters](https://docs.microsoft.com/powershell/module/sharepoint-online/new-spomigrationencryptionparameters) for more information.
Copy file name to clipboardExpand all lines: skype/skype-ps/skype/Disable-CsOnlineSipDomain.md
+20-7Lines changed: 20 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -13,11 +13,12 @@ ms.reviewer: rogupta
13
13
# Disable-CsOnlineSipDomain
14
14
15
15
## SYNOPSIS
16
+
16
17
This cmdlet prevents provisioning of users in Skype for Business Online for the specified domain. This cmdlet allows organizations with multiple on-premises deployments of Skype For Business Server or Lync Server to safely synchronize users from multiple forests into a single Office 365 tenant.
@@ -31,24 +32,31 @@ This cmdlet enables organizations with *multiple on-premises deployments of Skyp
31
32
This cmdlet facilitates consolidation of multiple Skype for Business Server deployments into a single Office 365 tenant. Consolidation can be achieved by moving one deployment at a time into Office 365, **provided the following key requirements are met**:
32
33
33
34
- There must be at most 1 O365 tenant involved. Consolidation in scenarios with >1 O365 tenant is not supported.
35
+
34
36
- At any given time, only 1 on-premises SfB forest can be in hybrid mode (Shared Sip Address Space) with Office 365. All other on-premises SfB forests must remain on-premises. (They presumably are federated with each other.)
37
+
35
38
- If 1 deployment is in hybrid mode, all sip domains from any other SfB forests must be disabled using this cmdlet before they can be synchronized into the tenant with Azure AD Connect. Users in all SfB forests other than the hybrid forest must remain on-premises.
39
+
36
40
- Organizations must fully migrate each SfB forest individually into the O365 tenant using hybrid mode (Shared Sip Address Space), and then detach the "hybrid" deployment, *before* moving on to migrate the next on-premises SfB deployment.
37
41
38
42
39
43
This cmdlet may also be useful for organizations with on-premises deployments of Skype for Business Server that have not properly configured Azure AD Connect. If the organization does not sync msRTCSIP-DeploymentLocator for its users, then Skype for Business Online will attempt to provision online any users with an assigned Skype for Business license, despite there being users on-premises. While the correct fix is to update the configuration for Azure AD Connect to sync those attributes, using Disable-CsOnlineSipDomain can also mitigate the problem until that configuration change can be made. If this cmdlet is run, any users that were previously provisioned online in that domain will be de-provisioned in Skype for Business Online.
40
44
41
-
**IMPORTANT**
42
-
This cmdlet should not be run for domains that contain users hosted in Skype for Business Online. Any users in a sip domain that are already provisioned *online* will cease to function if you disable the online sip domain:
45
+
> [!IMPORTANT]
46
+
> This cmdlet should not be run for domains that contain users hosted in Skype for Business Online. Any users in a sip domain that are already provisioned *online* will cease to function if you disable the online sip domain:
47
+
>
48
+
> - Their SIP addresses will be removed.
49
+
> - All contacts and meetings for these users hosted in Skype for Business Online will be deleted.
50
+
> - These users will no longer be able to login to the Skype for Business Online environment.
51
+
> - If these users use Teams, they will no longer be able to inter-operate with Skype for Business users, nor will they be able to federate with any users in other organizations.
43
52
44
-
- Their SIP addresses will be removed.
45
-
- All contacts and meetings for these users hosted in Skype for Business Online will be deleted.
46
-
- These users will no longer be able to login to the Skype for Business Online environment.
47
-
- If these users use Teams, they will no longer be able to inter-operate with Skype for Business users, nor will they be able to federate with any users in other organizations.
53
+
> [!NOTE]
54
+
> If the Tenant is disabled for Regionally Hosted Meetings in Skype for Business Online, Online SIP Domains must be disabled in all regions. You must execute this cmdlet in each region that is added in Allowed Data Location.
48
55
49
56
## EXAMPLES
50
57
51
58
### Example 1
59
+
52
60
```powershell
53
61
Disable-CsOnlineSipDomain -Domain Fabrikam.com
54
62
```
@@ -58,6 +66,7 @@ The cmdlet above disables the online sip domain Fabrikam.com. This would be usef
58
66
## PARAMETERS
59
67
60
68
### -Domain
69
+
61
70
The SIP domain to be disabled for online provisioning in Skype for Business Online.
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable.
108
120
For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
109
121
@@ -116,6 +128,7 @@ For more information, see [about_CommonParameters](https://go.microsoft.com/fwli
116
128
### None
117
129
118
130
## NOTES
131
+
119
132
This cmdlet is for advanced scenarios only. Organizations that are pure online or have only 1 on-premises deployment need not run this cmdlet.
Copy file name to clipboardExpand all lines: skype/skype-ps/skype/Enable-CsOnlineSipDomain.md
+18-4Lines changed: 18 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -13,30 +13,39 @@ ms.reviewer: rogupta
13
13
# Enable-CsOnlineSipDomain
14
14
15
15
## SYNOPSIS
16
+
16
17
This cmdlet enables provisioning of users in Skype for Business Online for the specified domain. This cmdlet is only necessary to run if you previously disabled a domain using Disable-CsOnlineSipDomain. Enable-CsOnlineSipDomain is used to facilitate consolidation of separate Skype for Business deployments into a single Office 365 tenant.
This cmdlet enables online provisioning of users in the specified SIP domain. In conjunction with Disable-CsOnlineSipDomain, this cmdlet allows organizations to consolidate *multiple on-premises deployments of Skype for Business Server (or Lync Server)* into a single Office 365 tenant. Consolidation can be achieved by moving one deployment at a time into Office 365, provided the following key requirements are met:
26
28
27
29
- There must be at most 1 O365 tenant involved. Consolidation for scenarios with > 1 O365 tenant is not supported.
30
+
28
31
- At any given time, only 1 on-premises SfB forest can be in hybrid mode (Shared Sip Address Space) with Office 365. All other on-premises SfB forests must remain on-premises. (They presumably are federated with each other.)
32
+
29
33
- If 1 deployment is in hybrid mode, all online SIP domains from any other SfB forests must be disabled before they can be synchronized into the tenant with Azure AD Connect. Users in all SfB forests other than the hybrid forest must remain on-premises.
34
+
30
35
- Organizations must fully migrate (e.g move all users to the cloud) each SfB forest individually into the O365 tenant using hybrid mode (Shared Sip Address Space), and then detach the "hybrid" deployment, *before* moving on to migrate the next on-premises SfB deployment.
31
36
32
37
Before running this cmdlet for any SIP domain in a Skype for Business Server deployment, you must complete migration of any other existing hybrid SfB deployment that is in progress. All users in an existing hybrid deployment must be moved to the cloud, and that existing hybrid deployment must be detached from Office 365, as described in this article: [Disable hybrid to complete migration to the cloud](https://docs.microsoft.com/skypeforbusiness/hybrid/cloud-consolidation-disabling-hybrid).
33
38
34
-
**IMPORTANT**
35
-
If you have more than one on-premises deployment of Skype for Business Server, you *must* ensure SharedSipAddressSpace is disabled in all other Skype for Business Server deployments except the deployment containing the SIP domain that is being enabled.
39
+
> [!IMPORTANT]
40
+
> If you have more than one on-premises deployment of Skype for Business Server, you *must* ensure SharedSipAddressSpace is disabled in all other Skype for Business Server deployments except the deployment containing the SIP domain that is being enabled.
41
+
42
+
> [!NOTE]
43
+
> If the Tenant is enabled for Regionally Hosted Meetings in Skype for Business Online, Online SIP Domains must be Enabled in all regions. You must execute this cmdlet in each region that is added in Allowed Data Location for Skype for Business.
36
44
37
45
## EXAMPLES
38
46
39
47
### Example 1
48
+
40
49
```powershell
41
50
Enable-CsOnlineSipDomain -Domain contoso.com
42
51
```
@@ -46,6 +55,7 @@ Enables the domain contoso.com for online provisioning in Skype for Business Onl
46
55
## PARAMETERS
47
56
48
57
### -Domain
58
+
49
59
The SIP domain to be enabled for online provisioning in Skype for Business Online.
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable.
106
+
107
+
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable,
108
+
-OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable.
95
109
For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
0 commit comments