Clatent

Technology | Fitness | Food

Sharepoint

365Automatedlab V2.10.1 Released!

by Leave a Comment

I know I said every 2 weeks, but I lied. I wanted to get this out! It is now possible to add a manager when creating a new user. Also added a feature so that when you use the parameter -UseDeveloperPackE5 when creating new users and it will add the Developer license to all added users.

New-CTUser

  • Added “Add Manager” when creating new user
  • Add only Dev licenses option
  • Updated help
  • Allow some parameters to be empty

Added “Discussions” in GitHub for feature requests and general discussions

Let me know what you think and if you have any feedback or suggestions!

Have a great day!

PowerShell Gallery: https://www.powershellgallery.com/packages/365AutomatedLab/2.10.1
GitHub: https://github.com/DevClate/365AutomatedLab

365Automatedlab V2.4.0 Released!

by Leave a Comment

Sorry I haven’t posted much, things have been a bit hectic, and I wish I could say a lot of behind the scene things for 365Automatedlab were because of it, but sadly it isn’t. Overall things are good, and glad to put out v2.4.0 which I’ve added a function to delete all “deleted” SharePoint sites the recycle bin. The reason for it is you can’t mass delete SharePoint sites from the GUI and sometimes you create SharePoint sites that aren’t in your Excel workbook and this just makes it easier.

Also wanted to post that in a few weeks, I’ll be speaking about 365AutomatedLab virtually and once I have all the info, I’ll post it up! Anything in particular you want to see?

PowerShell Gallery: 365AutomatedLab
GitHub: 365AutomatedLab

Have a great day!

365Automatedlab V2.3.0 Released!

by Leave a Comment

I had planned to publish an update sooner, but things got a bit crazy. Then I started prepping for my first PowerShell talk and ended up finding things to clean up and improve. I didn’t get much done on my presentation, but at least the module will run better. Hope you enjoy and please leave any feedback!

New Features

Export-CT365ProdUserToExcel

  • Default now includes Developer License
    • Use -NoLicense to remove

Export-CT365ProdTeamsToExcel

  • Exports Channel Type now
  • Exports Channel Descriptions now

Fixes

  • Updated function name for New-CT365DataEnvironment within ps1 file
  • Updated headers in New-CT365DataEnvironment to include Sites and Channels description.
  • Updated formatting of README

PowerShell Gallery: https://www.powershellgallery.com/packages/365AutomatedLab/2.3.0
GitHub: https://github.com/DevClate/365AutomatedLab

365Automatedlab V2.2.0 Released!

by Leave a Comment

Happy to announce the release of V2.2.0. Going forward I’ll post release updates here as well as on GitHub.

New Features:
New-CT365Teams: Updated to include Teams, Channels, and their owners. Currently it is set for the same owner for all, but will be updating it in the future. If you would like to see that sooner than later, please open an issue on GitHub.

Verify-CT365TeamsCreation: this is a private function to confirm that the Teams team was created successfully.

Breaking Changes:
None – There are no breaking changes in this update

How to use:

New-CT365Teams -FilePath “C:\Scripts\TeamsData.xlsx” -AdminUrl “testenv.sharepoint.com” -DefaultOwnerUPN “admin@testenv.com

This will create all Teams, Teams’ Channels, and set the owner to admin@testenv.com in the TeamsData.xlsx file under the worksheet name “Teams”. You can add more channels if needed if you follow the template and increase the channel number. For example, to add a Third channel, you would add 3 new columns, the first Channel3Name, the second Channel3Description, and the third Channel3Type with there correct value.

How to install: 

# Run first if you need to set Execution Policy
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

# Install 365AutomatedLab
Install-Module -Name 365AutomatedLab -Scope CurrentUser

Check out the GitHub Repo: 365AutomatedLab

If you have any questions, concerns, or feature requests, feel free to reach out to me and/or create a GitHub issue. I’m always looking for feedback on how I can improve this module to make it even more useful for you.

New Feature Announcement for 365AutomatedLab

by Leave a Comment

I wanted to let everyone know as of this morning you can add and remove Teams and Teams Channels with only 1 line of code and an Excel Worksheet using 365AutomatedLab.

It’s as simple as this:

New-CT365Teams -FilePath "C:\path\to\365DataEnvironment.xlsx" -AdminUrl "<https://yourdomain.sharepoint.com>"

And to remove those teams:

Remove-CT365Teams -FilePath "C:\path\to\365DataEnvironment.xlsx" -AdminUrl "<https://yourdomain.sharepoint.com>"

Let me know what you think. Do you want the ability to add more than 2 additional channels? Any of the other parameters you would like added for teams and channels? Eventually, I’ll add them all, but rather start with the ones that you most use.

As always feel free to reach out and I’m always open to PRs.

365AutomatedLab

Read-Only Friday 365 Developer Program

by Leave a Comment

Want to have some fun with Office 365, but don’t want to mess up your production environment? Or what about being able to try out scripts and not having to brace yourself as you run them and hope they don’t clear out all your data? Now you can do whatever you want with the Microsoft 365 Dev Center.

That is right, up to 25 E5 licensed users at your disposal for 90 days and will be renewed as long as you are using it. They will even create 16 users for you, mail traffic, and more. This isn’t just for PowerShell, this all aspects of 365.

Awesome, right? Here are few examples:

  1. You could copy up to 25 of your current users and import them into this Developer tenant and test scripts see exactly how it would work with your information. Think of those times where you test a script with fictional users and your script works perfect, but once you put it into production, your script fails because one username had a character that your test data didn’t have. Now your spending unnecessary time trying to figure out what went wrong when it worked perfectly in proof of concept.
  2. You want to test new features or policies, but you don’t want to enable them in your production environment, as your not 100% sure how it will react to your environment. Configure this test environment how your current tenant is then enable those features or policies you want to test. Much safer to test in the dev environment, then do it in production and all of a sudden your users can’t access critical resources or anything at all!
  3. Your boss wants you do a proof of concept on how to streamline the onboarding process and to make it as simple as possible for the organization. It is recommended that you use Sharepoint and Teams as the company already uses both and are familiar. Instead of using your production environment, you can do this all in the dev tenant without affecting anything in production. You can even invite key players in this project to login and test it with you. Now you don’t have to worry about a teams alert that you setup for when a new hire has been added to AD or Microsoft Entra ID spamming a your production channel because your script or flow errored.

These are just a few scenarios that the 365 Dev tenant can be useful, but there are so many more. I’m barely scratching the surface, and hope you sign up right away for this if you haven’t already. It is free, if you administer or develop 365, you need this.

I hope you found this helpful, and if you have any questions, I’d be glad to help out in anyway I can.

Sign up for the Microsoft 365 Dev Center