Who's Online
1 visitors online now
0 guests, 1 bots, 0 members
Support my Sponsor
  • An error has occurred, which probably means the feed is down. Try again later.

OneDrive App for Teams vs. Files in Old Teams

  1. Purpose and Usage:
    • OneDrive App for Teams:
      • Designed for individual workspace and personal file storage.
      • Ideal for files used by a single user.
      • Great for business documents, drafts, and personal reference.
    • Files in Old Teams:
      • Used for collaborative work within channels and teams.
      • Shared files accessible to multiple team members.
      • Suitable for ongoing projects and long-term collaborations.
  2. Access and Integration:
    • OneDrive App for Teams:
      • Seamlessly integrates with Teams.
      • Provides easy access to all Microsoft 365 content.
      • Replaces the existing Files menu item.
    • Files in Old Teams:
      • Accessed directly within Teams.
      • Linked to SharePoint libraries behind Teams and channels.
  3. File Ownership:
    • OneDrive App for Teams:
      • Files are owned by individual users.
      • Account holder’s departure doesn’t impact shared links.
    • Files in Old Teams:
      • Files are owned by the team or channel.
      • Shared links may be removed if the account holder leaves.
  4. Collaboration:
    • OneDrive App for Teams:
      • Limited sharing—best for personal use.
      • Collaboration features are minimal.
    • Files in Old Teams:
      • Robust collaboration tools.
      • Multiple users can work on shared files simultaneously.
  5. Future Enhancements:
    • The OneDrive app enhancements will roll out to classic Teams in early 2024, with the Files app name unchanged.

Workflow in Microsoft Teams

The Workflow feature enhances collaboration and productivity within Teams by streamlining processes and automating repetitive tasks. Here are some key aspects:

  1. Approvals and Reviews:
    • Teams now allows you to create approval workflows directly within channels or chats.
    • You can request approvals for documents, proposals, or any other content.
    • Approvers receive notifications and can review and respond without leaving Teams.
  2. Power Automate Integration:
    • Teams integrates seamlessly with Power Automate, Microsoft’s workflow automation platform.
    • You can create custom flows to automate actions based on triggers within Teams.
    • For example, automatically post a message in a channel when a new file is uploaded to a SharePoint folder.
  3. Templates and Custom Workflows:
    • Teams provides pre-built templates for common workflows.
    • Customize these templates or create your own workflows tailored to your team’s needs.
    • Examples include employee onboarding, expense approvals, and project management.
  4. Task Management:
    • Use the Tasks by Planner and To Do app to manage tasks within Teams.
    • Assign tasks, set due dates, and track progress—all without leaving the collaboration environment.
  5. Notifications and Reminders:
    • Workflow notifications keep team members informed.
    • Set reminders for upcoming deadlines, meetings, or important events.
  6. Integration with Apps and Bots:
    • Leverage third-party apps and bots to enhance workflows.
    • For instance, integrate with Trello, Jira, or other tools your team uses.

New features of Microsoft Teams V2

Also explained in Youtube Video : https://youtu.be/9jCqcvHY4lg

Let’s learn about new features of Microsoft Teams that enhance collaboration and productivity:

  1. Forward Chat Messages: Now, you can easily share chat messages by right-clicking any message and selecting “Forward.” No more manual copying and pasting—just smooth communication!
  2. Immersive Spaces with Microsoft Mesh: Imagine 3D immersive spaces within Teams meetings. It’s like teleporting to a virtual room where interactions feel more face-to-face. You can still use familiar Teams features like shared content, chat, and live reactions.
  3. Intelligent Recap with Copilot: If you’re a Microsoft 365 user with Copilot, get ready for intelligent recaps. These personalized timeline markers summarize meetings, making it a breeze to browse recordings based on relevant content.
  4. AI-Generated Backgrounds: Spice up your virtual meetings! Use AI to decorate your real-world room background. Clean up clutter, add plants, or create a serene oasis. Available for Teams Premium users.
  5. People-Specific Links for Collaborative Notes: Teams meetings now offer people-specific links for Collaborative Notes. These links provide more controlled access, aligning with specific file-sharing policies. Collaboration made smarter!
  6. Expanded Video Views: In Teams meetings on Chrome and Edge, you’ll automatically see up to 9 videos on your screen (previously limited to 4). Visual collaboration just got an upgrade!
  7. Simplified Audio and Video Controls: Adjust audio and video settings directly from the meeting controls. Volume, spatial audio, background—manage it all effortlessly.
  8. Agenda View : It is a scrollable list of your upcoming meetings in chronological order. It’s like having a neat to-do list for your meetings.
  9. Workflows : The Workflow feature enhances collaboration and productivity within Teams by streamlining processes and automating repetitive tasks. Explained in detail on This artice
  10. OneDrive : OneDrive Option is replacement of Files in old Teams. It comes with some advanced features which are explained in This Artice

Difference between Beta/me/profile and v1.0/me

Also explained in my Youtube video: https://www.youtube.com/watch?v=_XKrZvCIG98

The difference between the two endpoints is that https://graph.microsoft.com/beta/me/profile is in the beta version of the Microsoft Graph API, while https://graph.microsoft.com/v1.0/me is in the v1.0 version of the API . The beta version is used for testing new features and is not recommended for production use. The v1.0 version is the stable version of the API and is recommended for production use.

The https://graph.microsoft.com/beta/me/profile endpoint is used to retrieve information about a given user or yourself, such as the user’s profile information, interests, languages, skills, and more. To call this API, your app needs the appropriate permissions, such as User.Read.

On the other hand, the https://graph.microsoft.com/v1.0/me endpoint is used to retrieve information about the signed-in user, such as the user’s display name, email address, job title, and more. To call this API, your app needs the appropriate permissions, such as User.Read.

PowerShell to Add a user as admin on all site collections in SharePoint online

Also explained in my Youtube Video : https://youtu.be/icx_m15UIMg

You can modify this script to add these users as a member of visitor to all Site collections.

Connect to SharePoint Online

Connect-SPOService -Url https://contoso-admin.sharepoint.com

Get all site collections

$siteCollections = Get-SPOSite -Limit All

Loop through each site collection and add the user as an admin

foreach ($siteCollection in $siteCollections) {
Set-SPOUser -Site $siteCollection.Url -LoginName “[email protected]” -IsSiteCollectionAdmin $true
}

ConsistencyLevel:eventualError when using graphs API ‘count the guest users in your organization’

Explained the same in Youtube Video : https://youtu.be/TFcIbOKApwE

https://graph.microsoft.com/v1.0/users?$count=true&ConsistencyLevel=eventual&$filter=userType eq ‘Guest’

Read Microsoft Teams messages using Graphs API

Explained the same in Youtube Video : https://youtu.be/Uez9QrBNNS0

So today I had a requirement to create a custom app where I can read all MS teams message and use AI to reply to the team’s messages.

The 1st thing we need is to get read all Messages in Microsoft Teams using a Graphs API. I tried to look for option and finally got a Teams Beta API named ‘messages (Without replies) in a channel’ but it needs GroupID and ChannelID to read to the messages.

So I ran below Graphs API to get all the Teams I am members of, here we will get the name and the ID of the Teams group as well.

https://graph.microsoft.com/v1.0/me/joinedTeams

Now we need to use the Group ID in below graphs query to get allchannels in that teams group.

https://graph.microsoft.com/beta/teams/{group-id-for-teams}/Allchannels/

Finally when we have both the Group ID and ChannelID, we will use below graphs API to get all the messages in the ChannelID.

Note: I am only able to see all the unread messages.

https://graph.microsoft.com/beta/teams/{group-id-for-teams}/channels/{channel-id}/messages

Below I am able to see all the same messages using GUI in teams

Ways to add an item to SharePoint lists

Explained the same in Youtube Video : https://youtu.be/xioKl4KrlLo

To use Graph API to add content to a SharePoint list, you need to have the appropriate permissions, the site ID, the list ID, and the JSON representation of the list item you want to create. You can use the following HTTP request to create a new list item:

POST https://graph.microsoft.com/v1.0/sites/{site-id}/lists/{list-id}/items
Content-Type: application/json

{
  "fields": {
    // your list item properties
  }
}

To get site ID, use below URL
https://TenantName.sharepoint.com/sites/SiteName/_api/site

Here at the ID after HUBSiteID tag is actually your Site ID as shown below.

For example, if you want to create a list item with the title “Item2”, the color “Pink”, and the Number 1, you can use this JSON body:

{
  "fields": {
    "Title": "Item2",
    "Color": "Pink",
    "Number": 1
  }
}

If the request is successful, you will get a response with the created list item and its properties.

You can also use the Graph SDKs to simplify the process of creating list items in different programming languages. For example, here is how you can create a list item in C# using the Microsoft Graph SDK:

using Microsoft.Graph;
using Microsoft.Identity.Client;

// Create a public client application
var app = PublicClientApplicationBuilder.Create(clientId)
    .WithAuthority(authority)
    .Build();

// Get the access token
var result = await app.AcquireTokenInteractive(scopes)
    .ExecuteAsync();

// Create a Graph client
var graphClient = new GraphServiceClient(
    new DelegateAuthenticationProvider((requestMessage) =>
    {
        requestMessage
            .Headers
            .Authorization = new AuthenticationHeaderValue("bearer", result.AccessToken);

        return Task.CompletedTask;
    }));

// Create a dictionary of fields for the list item
var fields = new FieldValueSet
{
    AdditionalData = new Dictionary<string, object>()
    {
        {"Title", "Item"},
        {"Color", "Pink"},
        {"Number", 1}
    }
};

// Create the list item
var listItem = await graphClient.Sites[siteId].Lists[listId].Items
    .Request()
    .AddAsync(fields);

Import-Module : Function Remove-MgSiteTermStoreSetParentGroupSetTermRelation cannot be created because function capacity 4096 has been exceeded for this scope

Explained everything in the Video : https://youtu.be/7-btaMI6wJI

Today I got below error when I tried to import my Graphs module to Powershell (Import-Module Microsoft.Graph)

Import-Module : Function Remove-MgSiteTermStoreSetParentGroupSetTermRelation cannot be created because function capacity 4096 has been exceeded for this scope.
At line:1 char:1
+ Import-Module Microsoft.Graph
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (Remove-MgSiteTe...SetTermRelation:String) [Import-Module], SessionSta
   teOverflowException
    + FullyQualifiedErrorId : FunctionOverflow,Microsoft.PowerShell.Commands.ImportModuleCommand

After lot of research I identified that this is a known issue that occurs when importing Microsoft.Graph module in PowerShell 5.1, because the module has more than 4096 functions and PowerShell 5.1 has a limit on the number of functions that can be created in a scope.

There are some possible workarounds that you can try to resolve this error:

  • Upgrade to PowerShell 7+ or latest as the runtime version (highly recommended). PowerShell 7+ does not have the function capacity limit and can import the module without any errors.
  • Set $maximumfunctioncount variable to its max value, 32768, before importing the module. This will increase the function capacity limit for your scope, but it may not be enough if you have other modules loaded or if the Microsoft.Graph module adds more functions in the future.

    To check all Maximum value set in PowerShell
    gv Max*Count

    To set the Maximum Function Count
    $MaximumFunctionCount = 8096

I hope this helps you understand how to fix the error and import the Microsoft.Graph module successfully.

Classic application insights will be retired on 29 February 2024—migrate to workspace-based application insights

I recently got a email which says ‘Classic application insights will be retired on 29 February 2024—migrate to workspace-based application insights’.

Further it adds, classic application insights in Azure Monitor will be retired and you’ll need to migrate your resources to workspace-based application insights by that date.

Now if we move to Workspace-based application insights, it will offer improved functionality such as:

Now let’s logon to Azure and check what it means and how to migrate to workspace-based application insights.

Access the Application Insights and then click on ‘Classic Application Insights is deprecated and will be retired in February 2024. Migrate this resource to Workspace-based Application Insights to gain support for all of the capabilities of Log Analytics, including Customer-Managed Keys and Commitment Tiers. Click here to learn more and migrate in a few clicks’.

Now you will see the Subscription and the new Log Analytics Workspace getting created. Just click Apply at bottom of screen.

Once done, you will see the new workspace created and all the content of classic application.

You can also watch the whole process in my Youtube Video
https://www.youtube.com/watch?v=gvQp_33ezqg