-> Teams Copilot usage does not include Microsoft Copilot with Graph-grounded chat usage, but it will be displayed in Copilot for Microsoft 365 usage soon.

-## Before you begin

-To learn more about Microsoft 365 and work toward a Microsoft 365 certification, you can start with [Microsoft 365 Certified: Fundamentals](/training/paths/m365-fundamentals/).

-Another way to free up a license is by deleting the user account. For more information, see [Delete and restore user accounts with PowerShell](delete-and-restore-user-accounts-with-microsoft-365-powershell.md).

-## Use the Azure Active Directory PowerShell for Graph module

->The Set-AzureADUserLicense cmdlet is scheduled to be retired. Please migrate your scripts to the Microsoft Graph SDK's Set-MgUserLicense cmdlet as described above. For more information, see [Migrate your apps to access the license managements APIs from Microsoft Graph](https://techcommunity.microsoft.com/t5/azure-active-directory-identity/migrate-your-apps-to-access-the-license-managements-apis-from/ba-p/2464366).

->

-First, [connect to your Microsoft 365 tenant](connect-to-microsoft-365-powershell.md#connect-with-the-azure-active-directory-powershell-for-graph-module).

-Next, list the license plans for your tenant with this command.

-```powershell

-Get-AzureADSubscribedSku | Select SkuPartNumber

-```

-Next, get the sign-in name of the account for which you want to remove a license, also known as the user principal name (UPN).

-Finally, specify the user sign-in and license plan names, remove the "<" and ">" characters, and run these commands.

-```powershell

-$userUPN="<user sign-in name (UPN)>"

-$planName="<license plan name from the list of license plans>"

-$license = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicenses

-$license.RemoveLicenses = (Get-AzureADSubscribedSku | Where-Object -Property SkuPartNumber -Value $planName -EQ).SkuID

-Set-AzureADUserLicense -ObjectId $userUPN -AssignedLicenses $license

-```

-To remove all of the licenses for a specific user account, specify the user sign-in name, remove the "<" and ">" characters, and run these commands.

-```powershell

-$userUPN="<user sign-in name (UPN)>"

-$userList = Get-AzureADUser -ObjectID $userUPN

-$Skus = $userList | Select -ExpandProperty AssignedLicenses | Select SkuID

-if($userList.Count -ne 0) {

- if($Skus -is [array])

- {

- $licenses = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicenses

- for ($i=0; $i -lt $Skus.Count; $i++) {

- $licenses.RemoveLicenses += (Get-AzureADSubscribedSku | Where-Object -Property SkuID -Value $Skus[$i].SkuId -EQ).SkuID

- }

- Set-AzureADUserLicense -ObjectId $userUPN -AssignedLicenses $licenses

- } else {

- $licenses = New-Object -TypeName Microsoft.Open.AzureAD.Model.AssignedLicenses

- $licenses.RemoveLicenses = (Get-AzureADSubscribedSku | Where-Object -Property SkuID -Value $Skus.SkuId -EQ).SkuID

- Set-AzureADUserLicense -ObjectId $userUPN -AssignedLicenses $licenses

- }

-}

-```

-## Use the Microsoft Azure Active Directory module for Windows PowerShell

->[!Note]

->The Set-MsolUserLicense and New-MsolUser (-LicenseAssignment) cmdlets are scheduled to be retired. Please migrate your scripts to the Microsoft Graph SDK's Set-MgUserLicense cmdlet as described above. For more information, see [Migrate your apps to access the license managements APIs from Microsoft Graph](https://techcommunity.microsoft.com/t5/azure-active-directory-identity/migrate-your-apps-to-access-the-license-managements-apis-from/ba-p/2464366).

->

-First, [connect to your Microsoft 365 tenant](connect-to-microsoft-365-powershell.md#connect-with-the-microsoft-azure-active-directory-module-for-windows-powershell).

-To view the licensing plan (**AccountSkuID**) information in your organization, see the following articles:

-If you use the **Get-MsolUser** cmdlet without using the _-All_ parameter, only the first 500 accounts are returned.

-### Removing licenses from user accounts

-To remove licenses from an existing user account, use the following syntax:

-

-```powershell

-Set-MsolUserLicense -UserPrincipalName <Account> -RemoveLicenses "<AccountSkuId1>", "<AccountSkuId2>"...

-```

->[!Note]

->PowerShell Core does not support the Microsoft Azure Active Directory module for Windows PowerShell module and cmdlets with **Msol** in their name. To continue using these cmdlets, you must run them from Windows PowerShell.

->

-This example removes the **litwareinc:ENTERPRISEPACK** (Office 365 Enterprise E3) license from the user account BelindaN@litwareinc.com.

-

-```powershell

-Set-MsolUserLicense -UserPrincipalName belindan@litwareinc.com -RemoveLicenses "litwareinc:ENTERPRISEPACK"

-```

->[!Note]

->You cannot use the `Set-MsolUserLicense` cmdlet to unassign users from *canceled* licenses. You must do this individually for each user account in the Microsoft 365 admin center.

->

-To remove all licenses from a group of existing licensed users, use either of the following methods:

-

- ```powershell

- $userArray = Get-MsolUser -All <FilterableAttributes> | where {$_.isLicensed -eq $true}

- for ($i=0; $i -lt $userArray.Count; $i++)

- {

- Set-MsolUserLicense -UserPrincipalName $userArray[$i].UserPrincipalName -RemoveLicenses $userArray[$i].licenses.accountskuid

- }

- ```

- This example removes all licenses from all user accounts in the Sales department in the United States.

- ```powershell

- $userArray = Get-MsolUser -All -Department "Sales" -UsageLocation "US" | where {$_.isLicensed -eq $true}

- for ($i=0; $i -lt $userArray.Count; $i++)

- {

- Set-MsolUserLicense -UserPrincipalName $userArray[$i].UserPrincipalName -RemoveLicenses $userArray[$i].licenses.accountskuid

- }

- ```

- 1. Create and save a text file that contains one account on each line like this:

- 2. Use the following syntax:

- ```powershell

- $x=Get-Content "<FileNameAndPath>"

- for ($i=0; $i -lt $x.Count; $i++)

- {

- Set-MsolUserLicense -UserPrincipalName $x[$i] -RemoveLicenses "<AccountSkuId1>","<AccountSkuId2>"...

- }

- ```

- This example removes the **litwareinc:ENTERPRISEPACK** (Office 365 Enterprise E3) license from the user accounts defined in the text file C:\My Documents\Accounts.txt.

- Set-MsolUserLicense -UserPrincipalName $x[$i] -RemoveLicenses "litwareinc:ENTERPRISEPACK"

- }

- ```

- To remove all licenses from all existing user accounts, use the following syntax:

-

- ```powershell

- $userArray = Get-MsolUser -All | where {$_.isLicensed -eq $true}

- for ($i=0; $i -lt $userArray.Count; $i++)

- {

- Set-MsolUserLicense -UserPrincipalName $userArray[$i].UserPrincipalName -RemoveLicenses $userArray[$i].licenses.accountskuid

-| [False positive](defender-endpoint-false-positives-negatives.md): An entity, such as a file or a process, was detected and identified as malicious, even though the entity isn't a threat. | 1. [Review and classify alerts](defender-endpoint-false-positives-negatives.md#part-1-review-and-classify-alerts) that were generated as a result of the detected entity. <br/>2. [Suppress an alert](defender-endpoint-false-positives-negatives.md#suppress-an-alert) for a known entity. <br/>3. [Review remediation actions](defender-endpoint-false-positives-negatives.md#part-2-review-remediation-actions) that were taken for the detected entity. <br/>4. [Submit the false positive to Microsoft](../intelligence/submission-guide.md) for analysis. <br/>5. [Define an exclusion](defender-endpoint-false-positives-negatives.md#part-3-review-or-define-exclusions) for the entity (only if necessary). |

-description: There are various collaborative programs regarding Microsoft industry-wide anti-malware - Microsoft Virus Initiative (MVI), and Coordinated Malware Eradication (CME)

-keywords: security, malware, antivirus industry, anti-malware Industry, collaboration programs, alliances, Microsoft Virus Initiative, Coordinated Malware Eradication, WDSI, MMPC, Microsoft Malware Protection Center, partnerships

-ms.sitesec: library

-# Industry collaboration programs

-There are various industry-wide collaboration programs with different objectives and requirements, provided by Microsoft. Enrolling in the right program can help you protect your customers, gain more insight into the current threat landscape, or help disrupting the malware ecosystem.

-## Microsoft Virus Initiative (MVI)

-MVI is open to organizations who build and own a Real Time Protection (RTP) anti-malware product of their own design, or one developed using a third-party Antivirus SDK.

-Members get access to the [Microsoft Defender XDR APIs](../defender/api-overview.md) for the Microsoft Defender portal, IOfficeAntivirus (IOAV), AntiMalware Scan Interface (AMSI), and Cloud Files, along with health data and other telemetry to help customers stay protected. Anti-malware products are submitted to Microsoft for performance testing regularly.

-Go to the [MVI program page](virus-initiative-criteria.md) for more information.

-## Coordinated Malware Eradication (CME)

-CME is open to organizations who are involved in cybersecurity and anti-malware or interested in fighting cybercrime.

-The program aims to bring organizations in cybersecurity and other industries together to pool tools, information, and actions to drive coordinated campaigns against malware. The ultimate goal is to create efficient and long-lasting results for better protection of our communities, customers, and businesses.

-Go to the [CME program page](coordinated-malware-eradication.md) for more information.

-|**Show first contact safety tip** (_EnableFirstContactSafetyTips_)|Selected (`$true`)|Not selected (`$false`)|

-Admins can use the sample submission portal at <https://www.microsoft.com/wdsi/filesubmission> to submit other suspected files to Microsoft for analysis. For more information, see [Submit files for analysis](../intelligence/submission-guide.md).

-description: Learn about Microsoft SharePoint eSignature and how to send electronic signature requests to people inside and outside of your organization.

-# Overview of Microsoft SharePoint eSignature

-description: Learn how to review and sign electronic signature requests using Microsoft SharePoint eSignature.

-# Review and sign a signature request using Microsoft SharePoint eSignature

-description: Learn how to use Microsoft SharePoint eSignature to create and send electronic signature requests to people inside and outside of your organization.

-# Create a signature request using Microsoft SharePoint eSignature

-description: Learn how to set up and manage sites in Microsoft SharePoint eSignature.

-# Set up Microsoft SharePoint eSignature

-> Microsoft SharePoint eSignature is currently rolling out to the US market. If a tenant's location is the United States, SharePoint eSignature will be available for that tenant. For US-located, multi-geo enabled tenants, eSignature will be available in the home geo only. SharePoint eSignature will roll out to other regions in 2024.

-The SharePoint eSignature service is set up in the Microsoft 365 admin center. SharePoint eSignature uses simple electronic signatures. Before you begin, determine whether this feature is appropriate for your needs and then read the [Microsoft SharePoint eSignature terms of service](/legal/microsoft-365/esignature-terms-of-service).

-description: Learn how to troubleshoot issues with sending, receiving, or viewing requests in Microsoft SharePoint eSignature.

-# Troubleshoot a signature request for Microsoft SharePoint eSignature

-The PDF viewer is opened by selecting a PDF file from SharePoint Online. The ability to use the **Get signatures** option won't be available if the PDF is viewed in any other way, for example, in Microsoft Edge or Adobe Reader.

-Certain [conditional access](/entra/identity/conditional-access/overview) policies might determine whether an external recipient (signers outside of your organization or Microsoft 365 tenant) will be able sign a document. When this happens, the external signers might not be able to access the document for signing. In some other cases, they might be able to access the document for signing but the signing operation will be unsuccessful. One common way to resolve this is to contact your IT admin who will be able to add the eSignature app to the list of approved apps via the Microsoft Entra admin center.

-## Unable to find the request emails

-If you were sent an eSignature request and cannot find it in your email inbox, you should check your spam or junk folder. It is also good practice to mark the sender as non-spam so that future emails from the same sender go directly into your inbox.

-Before a signature request is sent and at the completion of the request, certain checks are done to ensure that the sender has the permissions to write to the document and the originating folder because the final signed document is saved in this folder. If the sender loses access to this folder at any point before signing is complete, they might not be able to access the signed document permanently. In this scenario, the sender will be provided temporary access of 30 days to the signed document through the completion email. To access the folder and document, the sender should ensure that they have read permission to the originating folder or request access from the owner.