Home

PowerShell Module for Microsoft Teams got released

%3CLINGO-SUB%20id%3D%22lingo-sub-124080%22%20slang%3D%22en-US%22%3EPowerShell%20Module%20for%20Microsoft%20Teams%20got%20released%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-124080%22%20slang%3D%22en-US%22%3E%3CP%3EFor%20the%20Office%20365%20Admins%20out%20there%2C%20the%20PowerShell%20module%20for%20Microsoft%20Teams%20just%20got%20released%20%26gt%3B%20%3CA%20href%3D%22https%3A%2F%2Fwww.powershellgallery.com%2Fpackages%2FMicrosoftTeams%2F0.9.0%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.powershellgallery.com%2Fpackages%2FMicrosoftTeams%2F0.9.0%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you're%20interested%2C%20you%20can%20also%20view%20a%20quick%20Overview%20of%20the%20cmdlets%20that%20I%20did%20on%20my%20blog%20over%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fabsolute-sharepoint.com%2F2017%2F11%2Fquick-overview-of-the-new-microsoft-teams-powershell.html%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fabsolute-sharepoint.com%2F2017%2F11%2Fquick-overview-of-the-new-microsoft-teams-powershell.html%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20didn't%20find%20the%20official%20Microsoft%20Documentation%20for%20the%20cmdlets%20yet%2C%20so%20maybe%20someone%20at%20MS%20can%20help%20us%20find%20it%20%3A)%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20a%20more%20personal%20question%2C%20I%20am%20wondering%20what%20do%20people%20look%20forward%20to%20automating%20with%20PowerShell%20and%20MS%20Teams%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-124080%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-353818%22%20slang%3D%22en-US%22%3ERe%3A%20PowerShell%20Module%20for%20Microsoft%20Teams%20got%20released%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-353818%22%20slang%3D%22en-US%22%3EIt%20seems%20you%20have%20the%2032%20bit%20version%20of%20powershell!%3CBR%20%2F%3E%3CBR%20%2F%3ETry%20Install%20the%2064%20bit%20version%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-353804%22%20slang%3D%22en-US%22%3ERe%3A%20PowerShell%20Module%20for%20Microsoft%20Teams%20got%20released%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-353804%22%20slang%3D%22en-US%22%3E%3CP%3EI%20want%20to%20use%20the%20Teams%20module%20in%20my%20Azure%20function%20-%20I%20use%20PnP%20and%20SPO%20modules%20already.%3C%2FP%3E%3CP%3EUnfortunately%20when%20loading%20the%20module%2C%20it%20reports%20an%20error%20like%20this%3A%3C%2FP%3E%3CP%3EImport-Module%20%3A%20The%20current%20processor%20architecture%20is%3A%20X86.%20The%20module%20'D%3A%5Chome%5Csite%5Cwwwroot%5C...%5Cmodules%5CMicrosoftTeams%5C0.9.3%5CMicrosoftTeams.psd1'%20requires%20the%20following%20architecture%3A%20Amd64.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20can%20I%20do%20about%20this%20problem%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3CP%3ELeif%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-264245%22%20slang%3D%22en-US%22%3ERe%3A%20PowerShell%20Module%20for%20Microsoft%20Teams%20got%20released%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-264245%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20module%20is%20great%20for%20admin%20of%20Teams%2C%20but%20now%20to%20automate%20things%20like%20messages...%20Flow%20might%20be%20the%20route%20for%20that%20but%20I%20am%20looking%20at%20a%20task%20in%20VSCode%20where%20I%20can%20update%20a%20working%20copy%20of%20a%20snippet%20file%2C%20then%20the%20task%20posts%20it%20to%20a%20shared%20location%20and%20I%20would%20like%20to%20post%20a%20message%20in%20a%20team%20channel%20(via%20Webhook%20or%20native)%20to%20notify%20team%20members.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-207974%22%20slang%3D%22en-US%22%3ERe%3A%20PowerShell%20Module%20for%20Microsoft%20Teams%20got%20released%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-207974%22%20slang%3D%22en-US%22%3E%3CP%3EMFA%20support%20is%20integrated%20into%20the%20module%2C%20just%20tested%20this.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-203098%22%20slang%3D%22en-US%22%3ERe%3A%20PowerShell%20Module%20for%20Microsoft%20Teams%20got%20released%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-203098%22%20slang%3D%22en-US%22%3E%3CP%3EHere's%20the%20documentation%20that%20i%20found%20helpful%20on%20this%20topic%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fskypehybridguy%2F2017%2F11%2F07%2Fmicrosoft-teams-powershell-support%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.technet.microsoft.com%2Fskypehybridguy%2F2017%2F11%2F07%2Fmicrosoft-teams-powershell-support%2F%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-179412%22%20slang%3D%22en-US%22%3ERe%3A%20PowerShell%20Module%20for%20Microsoft%20Teams%20got%20released%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-179412%22%20slang%3D%22en-US%22%3E%3CP%3Edo%20you%20have%20any%20powershell%20to%20connect%20microsoft%20teams%20with%20mfa%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-174027%22%20slang%3D%22en-US%22%3ERe%3A%20PowerShell%20Module%20for%20Microsoft%20Teams%20got%20released%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-174027%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20there%20a%20way%20to%20change%20video%20quality%20for%20the%20teams%20client%20like%20there%20was%20in%20skype%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-144759%22%20slang%3D%22en-US%22%3ERe%3A%20PowerShell%20Module%20for%20Microsoft%20Teams%20got%20released%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-144759%22%20slang%3D%22en-US%22%3E%3CP%3EYep.%20My%20intention%20wasn't%20to%20create%20a%20complete%20solution%2C%20just%20to%20prove%20the%20principle.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-144746%22%20slang%3D%22en-US%22%3ERe%3A%20PowerShell%20Module%20for%20Microsoft%20Teams%20got%20released%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-144746%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20would%20have%20to%20run%20that%20script%20per%20user%2C%20correct%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-144152%22%20slang%3D%22en-US%22%3ERe%3A%20PowerShell%20Module%20for%20Microsoft%20Teams%20got%20released%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-144152%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20Teams%20PowerShell%20module%20doesn't%20have%20the%20functionality%20that%20you%20want%20(see%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.petri.com%2Fteams-powershell-primer%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.petri.com%2Fteams-powershell-primer%3C%2FA%3E%20for%20more%20information)%2C%20but%20Office%20365%20has%20many%20ways%20to%20skin%20the%20proverbial%20cat...%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHere's%20an%20example%20from%20the%20%3CA%20href%3D%22https%3A%2F%2Fpractical365.com%2Febooks%2Foffice-365-for-it-pros%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EOffice%20365%20for%20IT%20Pros%20%3C%2FA%3E(4th%20ed.)%20ebook%20(one%20of%20941%20examples%20in%20the%20book).%20The%20code%20uses%20the%20Teams%20audit%20records%20in%20the%20Office%20365%20audit%20log%20to%20search%20for%20sign-in%20events.%20If%20any%20are%20found%20for%20a%20user%2C%20it%20reports%20the%20fact%20like%20this%3A%3C%2FP%3E%0A%3CP%3E%3CEM%3E%3CSTRONG%3ELast%20audit%20record%20for%20kim.akers%40office365itpros.com%20generated%20by%20signing%20into%20Teams%20was%2008%2F01%2F2018%2015%3A10%3A23%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt%20might%20do%20what%20you%20want%20or%20at%20least%20give%20you%20the%20basis%20of%20a%20solution...%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%3E%24CheckUser%20%3D%20(Read-Host%20%22user%20to%20check%22)%0A%24StartCheckDate%20%3D%20(Get-Date).AddDays(-30)%0A%24Today%20%3D%20(Get-Date)%0A%24AuditRecs%20%3D%20(Search-UnifiedAuditLog%20-RecordType%20MicrosoftTeams%20-StartDate%20%24StartCheckDate%20-EndDate%20%24Today%20-Operations%20TeamsSessionStarted%20-UserIds%20%24CheckUser%20-SessionCommand%20ReturnNextPreviewPage%20)%0AIf%20(%24AuditRecs.Count%20-gt%200)%20%7B%20Write-Host%20%22Last%20audit%20record%20for%22%20%24CheckUser%20%22generated%20by%20signing%20into%20Teams%20was%22%20%24AuditRecs%5B0%5D.CreationDate%20%7D%3C%2FPRE%3E%0A%3CP%3Ei%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-143938%22%20slang%3D%22en-US%22%3ERe%3A%20PowerShell%20Module%20for%20Microsoft%20Teams%20got%20released%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-143938%22%20slang%3D%22en-US%22%3E%3CP%3EI%20need%20to%20be%20able%20to%20manage%20external%20users%20better%20both%20in%20Teams%20and%20regular%20SharePoint%20sites.%26nbsp%3B%20Just%20getting%20a%20list%20of%20external%20users%20doesn't%20help.%26nbsp%3B%20I%20need%20to%20be%20able%20to%20see%20which%20external%20users%20haven't%20logged%20in%20over%20a%20period%20of%20time.%26nbsp%3B%20So%20a%20parameter%20for%20a%20date%20would%20be%20awesome.%26nbsp%3B%20I've%20discovered%20that%20deleting%20a%20Team%20Group%20site%20deletes%20the%20O365%20group%20but%20it%20doesn't%20remove%20the%20external%20user%20that%20was%20added%20to%20the%20group.%20That%20user%20remain%20in%20O365%20users.%26nbsp%3B%20Please%20HELP!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-138945%22%20slang%3D%22en-US%22%3ERe%3A%20PowerShell%20Module%20for%20Microsoft%20Teams%20got%20released%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-138945%22%20slang%3D%22en-US%22%3E%3CP%3EI%20agree%20this%20is%20very%20frustrating%2C%20and%20supports%20Tony's%20point%20that%20the%20Teams%20module%20seems%20to%20be%20coming%20from%20a%20user%20perspective%20rather%20than%20an%20admin%20perspective.%20Hopefully%20this%20will%20change%20soon%2C%20and%20a%20company%20admin%20will%20be%20able%20to%20connect%20and%20manage%20teams%20without%20a%20license%20or%20team%20membership.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-138942%22%20slang%3D%22en-US%22%3ERe%3A%20PowerShell%20Module%20for%20Microsoft%20Teams%20got%20released%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-138942%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20write-up%20on%20this%20topic.%20I'm%20just%20looking%20at%20the%20Teams%20automation%20capabilities%20and%20running%20into%20the%20same%20issues.%20Some%20comments%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERegarding%20the%20similarity%20to%20the%20AzureAD%20module%20-%20another%20PITA%20%3A(%3C%2Fimg%3E%20-%20I%20think%20this%20is%20because%20of%20the%20reliance%20on%20the%20Graph%20API%20and%20its%20limited%20filtering%20capabilities.%20AzureAD%20relies%20on%20oData%20filtering%2C%20and%20it%20doesn't%20even%20support%20the%20full%20set%20of%20features%20in%20that%20regard.%20The%20UnifiedGroup%20cmdlets%20probably%20have%20better%20support%20for%20this%20because%20they're%20using%20Exchange%20instead%20of%20the%20Graph%20API%20(an%20assumption).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20see%20that%20the%20Get-Team%20cmdlet%20does%20have%20a%20parameter%20-User%2C%20but%20it%20seems%20to%20be%20currently%20not%20supported.%20When%20I%20run%20it%20get%20the%20error%20message%20%22This%20request%20is%20supported%20in%20current%20user%20context%20only.%22%20I'm%20hopeful%20that%20this%20means%20that%20MS%20is%20working%20toward%20making%20this%20a%20more%20admin-centric%20module%20by%20v1.0%20release.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-132609%22%20slang%3D%22en-US%22%3ERe%3A%20PowerShell%20Module%20for%20Microsoft%20Teams%20got%20released%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-132609%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3Ehow%20is%20it%20possible%20that%20as%20a%20Global%20admin%20with%20dedicated%20AD%20account%2C%20I%20need%20to%20assign%20a%20license%20to%20my%20admin%20user%20in%20order%20to%20use%20the%20PowerShell%20commands.%20I%20am%20not%20willing%20to%20pay%20a%20license%20just%20for%20that%2C%20not%20required%20by%20any%20other%20admin%20interface%20to%20O365%20via%20PowerShell%3C%2FP%3E%0A%3CP%3EUpdate%3A%20I%20assigned%20myself%20a%20license%20to%20find%20out%20that%20this%20is%20not%20even%20an%20admin%20interface.%20Wrong%20expectations%20I%20guess%2C%20but%20I%20will%20tell%20my%20users%20to%20use%20PowerShell%20for%20controlling%20their%20Teams%20%3A)%3C%2Fimg%3E%3C%2FP%3E%0A%3CP%3EBest%3C%2FP%3E%0A%3CP%3EMartin%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-125476%22%20slang%3D%22en-US%22%3ERe%3A%20PowerShell%20Module%20for%20Microsoft%20Teams%20got%20released%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-125476%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20view%20of%20this%20module%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EWhy%20the%20PowerShell%20Module%20for%20Teams%20is%20Critically%20Flawed%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%20has%20released%20a%20beta%20version%20of%20the%20Teams%20PowerShell%20module.%20The%20only%20problem%20is%20that%20the%20module%20is%20not%20very%20good.%20In%20fact%2C%20the%20module%20is%20very%20disappointing%20because%20it%20does%20not%20contain%20the%20cmdlets%20that%20an%20Office%20365%20administrator%20might%20except%20to%20automate%20operations%20around%20Teams.%20Maybe%20the%201.0%20release%20will%20be%20better.%20We%20can%20only%20hope!%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.petri.com%2Fpowershell-module-teams-critically-flawed%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.petri.com%2Fpowershell-module-teams-critically-flawed%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Vlad Catrinescu
MVP

For the Office 365 Admins out there, the PowerShell module for Microsoft Teams just got released > https://www.powershellgallery.com/packages/MicrosoftTeams/0.9.0 

 

If you're interested, you can also view a quick Overview of the cmdlets that I did on my blog over here: https://absolute-sharepoint.com/2017/11/quick-overview-of-the-new-microsoft-teams-powershell.html 

 

I didn't find the official Microsoft Documentation for the cmdlets yet, so maybe someone at MS can help us find it :)? 

 

On a more personal question, I am wondering what do people look forward to automating with PowerShell and MS Teams? 

 

15 Replies

My view of this module:

 

Why the PowerShell Module for Teams is Critically Flawed

 

Microsoft has released a beta version of the Teams PowerShell module. The only problem is that the module is not very good. In fact, the module is very disappointing because it does not contain the cmdlets that an Office 365 administrator might except to automate operations around Teams. Maybe the 1.0 release will be better. We can only hope!

https://www.petri.com/powershell-module-teams-critically-flawed

Hi,

how is it possible that as a Global admin with dedicated AD account, I need to assign a license to my admin user in order to use the PowerShell commands. I am not willing to pay a license just for that, not required by any other admin interface to O365 via PowerShell

Update: I assigned myself a license to find out that this is not even an admin interface. Wrong expectations I guess, but I will tell my users to use PowerShell for controlling their Teams :)

Best

Martin

Good write-up on this topic. I'm just looking at the Teams automation capabilities and running into the same issues. Some comments:

 

Regarding the similarity to the AzureAD module - another PITA :( - I think this is because of the reliance on the Graph API and its limited filtering capabilities. AzureAD relies on oData filtering, and it doesn't even support the full set of features in that regard. The UnifiedGroup cmdlets probably have better support for this because they're using Exchange instead of the Graph API (an assumption).

 

I see that the Get-Team cmdlet does have a parameter -User, but it seems to be currently not supported. When I run it get the error message "This request is supported in current user context only." I'm hopeful that this means that MS is working toward making this a more admin-centric module by v1.0 release.

I agree this is very frustrating, and supports Tony's point that the Teams module seems to be coming from a user perspective rather than an admin perspective. Hopefully this will change soon, and a company admin will be able to connect and manage teams without a license or team membership.

I need to be able to manage external users better both in Teams and regular SharePoint sites.  Just getting a list of external users doesn't help.  I need to be able to see which external users haven't logged in over a period of time.  So a parameter for a date would be awesome.  I've discovered that deleting a Team Group site deletes the O365 group but it doesn't remove the external user that was added to the group. That user remain in O365 users.  Please HELP!

The Teams PowerShell module doesn't have the functionality that you want (see https://www.petri.com/teams-powershell-primer for more information), but Office 365 has many ways to skin the proverbial cat...

 

Here's an example from the Office 365 for IT Pros (4th ed.) ebook (one of 941 examples in the book). The code uses the Teams audit records in the Office 365 audit log to search for sign-in events. If any are found for a user, it reports the fact like this:

Last audit record for kim.akers@office365itpros.com generated by signing into Teams was 08/01/2018 15:10:23

 

It might do what you want or at least give you the basis of a solution...

 

$CheckUser = (Read-Host "user to check")
$StartCheckDate = (Get-Date).AddDays(-30)
$Today = (Get-Date)
$AuditRecs = (Search-UnifiedAuditLog -RecordType MicrosoftTeams -StartDate $StartCheckDate -EndDate $Today -Operations TeamsSessionStarted -UserIds $CheckUser -SessionCommand ReturnNextPreviewPage )
If ($AuditRecs.Count -gt 0) { Write-Host "Last audit record for" $CheckUser "generated by signing into Teams was" $AuditRecs[0].CreationDate }

You would have to run that script per user, correct?

Yep. My intention wasn't to create a complete solution, just to prove the principle.

Is there a way to change video quality for the teams client like there was in skype?

do you have any powershell to connect microsoft teams with mfa

MFA support is integrated into the module, just tested this.

This module is great for admin of Teams, but now to automate things like messages... Flow might be the route for that but I am looking at a task in VSCode where I can update a working copy of a snippet file, then the task posts it to a shared location and I would like to post a message in a team channel (via Webhook or native) to notify team members.

I want to use the Teams module in my Azure function - I use PnP and SPO modules already.

Unfortunately when loading the module, it reports an error like this:

Import-Module : The current processor architecture is: X86. The module 'D:\home\site\wwwroot\...\modules\MicrosoftTeams\0.9.3\MicrosoftTeams.psd1' requires the following architecture: Amd64.

 

What can I do about this problem?

 

Regards

Leif

It seems you have the 32 bit version of powershell!

Try Install the 64 bit version
Related Conversations