Code Monkey home page Code Monkey logo

microsoft-365-community's Introduction

Welcome to the Microsoft 365 Community Docs

Introduction

This repository is here for YOU. The goal is to build an open source set of content to help people like Information Architects, Business Analysts, "Makers" (aka Citizen Developers), and Site Owners who want to use the Microsoft 365 platform better.

There are lots of other resources for developers, so that isn't our target audience. We may include some code samples or snippets of code in the context of getting something done, but for the most part, any code in this repository will exist to help facilitate conversations between the folks listed above and the developers with whom they work.

This content is available in the Microsoft 365 Community Docs. Contribute and be a part of history!

Questions & Help

If you are looking for documentation about something which you feel fits this mold but are coming up short, here are some things you can do by raising an Issue in the Issues list:

  • Explain what you need and why, but be realistic about the time frames in which you may see a result. This is an open source effort and we all have day jobs.
  • Suggest an article or set of articles you've seen in blogs or other electronic formats which you think start(s) to get at the issue and might make a good addition here.
  • Write something to fill the gap. Whether it's a germ of an explanation or a full-fledged article, whatever you write can add value to the repository.

Updates & Feedback

To keep track of Microsoft 365 Community Docs updates, please follow us:

Have Fun

While we want the content in this repository to be extremely useful, it doesn't need to be dry and flavorless. We want to characterize the feel and joy of getting things done well in addition to the mechanics. Specific examples or analogies can be very useful to make this happen.

Contributing

This repository is sanctioned by Microsoft and therefore there are some contribution guidelines to follow. If you want to contribute to the discussions, ideas, or articles, you need to have a Github account. We do not want Github to be a barrier to your contributions. If you are new to Github and have ideas you would like to submit outside GitHub, add a post to the Discussions. We can work together to get your contribution into the repo. If you want to learn how to contribute through Github, check out our step-by-step guide with videos for Contributing to Microsoft Community Docs or explore the Wiki articles for more details on the mechanics of contributing.


This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

microsoft-365-community's People

Contributors

aditisrivastava07 avatar american-dipper avatar ashikpaul avatar bigpix2000 avatar daisyfell avatar dstrome avatar eemancini avatar efrene avatar garycentric avatar helloitsliam avatar jimmyhang avatar joannehendrickson avatar luisefreese avatar michaelroth42 avatar modery avatar nyoung30 avatar patd avatar pathtosharepoint avatar pkbullock avatar prasadkasireddy avatar samanro avatar sharonweaver avatar simondoy avatar simonjhudson avatar stacyrch140 avatar sympmarc avatar usermanagedsolutions avatar v-sidlama avatar v-stsavell avatar veronicageek avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

microsoft-365-community's Issues

Explaining content type propagation

Article suggestion

Explanation of how content types and site columns can be propagated through a site with sub sites and throughout a tenant. Different approaches e.g. Enterprise Content Types, Site Collection level content types, how these can be setup and deployed. Pros/Cons for approaches allowing a decision to make based on their business scenario.

Information Architecture - Managed Metadata

Article suggestion

Managed metadata is provided by the taxonomy service, and thus is potentially available for use across all sites in the tenant. We used to use lookup columns a lot; can managed metadata replace them completely? What are the pros and cons?

Organization of Docs in Cards on 'Microsoft 365 Community Content'

From @veronicageek:

Looking at the M365 Community Docs, I was wondering if maybe, we could put the articles in alphabetical order or something inside of their group (Basics, IA, etc…)?
I think it would be easier… Knowing that when you’re on that page and you search, it’s actually not scoped to the Community Docs 😕

How should organizations decide what to use for org-wide communications?

Article suggestion

Tony Redmond did a post about Microsoft’s Bad Idea to Create an Org-Wide Team for New Office 365 Tenants

“Microsoft has announced their intention to create an org-wide team for new small to medium tenants with under 5,000 users. This might help Teams, but it’s a horrible idea on many levels. Microsoft has no idea whether a new tenant wants to use Teams at all, so stuffing Teams down their throat doesn’t seem wise.“

Given that, how should organizations decide what to use for org-wide communications? There are multiple options: an org-wide Team, Yammer, News on the SharePoint home page, email to a DL, etc. What criteria do orgs need to think through to be successful? (Hint: it probably will require some change management.)

Importing data into SharePoint

Article suggestion

Site Owners should be ready to assist, and encourage, end-users with getting their existing stuff into SharePoint.

Think it should be scoped to methods, not metadata/folder nuances. Would like to see an article on the methods both front-end-center (dragging and dropping folders) and power-user focused (Excel-export to SharePoint?).

SharePoint Permissions vs. Office 365 Group Site Permissions

Article suggestion

We've blown countless cycles on figuring out the relationship (or lack there-of) between old-world style SharePoint permissions, and the Members/Owners style permissions in a Group SPO site. Feel like we can't be the only ones.

I think the target for this article might be "Site Owner who's done On-Prem permission work and is thrown into the SPO lifestyle"

This one could get wordy quickly - interested in suggestions for a narrower scope.

Information Architecture - Site Topology

Article suggestion

Why do you need to think about your site topology, even in the flat, modern world? How is it different than classic SharePoint? How important are things like name spacing and naming conventions?

Library scenarios

Got a great end to end scenario for using SharePoint libraries? We could establish some community practices and patterns.

Describe KFM Benefits for end users

Category

  • Question
  • Article suggestion
  • Article issue

Article suggestion

KFM is a great capability, but none of the existing documentation describes it from an end user perspective.

Content Weight of Modern Communication SharePoint Sites

Article suggestion

When designing communication sites, intranets for example some of the look books, the consideration of the amount of content required to implement the design.

Article could contain some planning considerations with an example of a look book page, with estimate amount of minimum content to achieve a design.

Sharing is caring.

How Do Site Columns Become Managed Properties - Thus Available for Search?

Article suggestion

From this Twitter thread from Darrell Miller:

If I create a site column based on a termset, will it create a managed property that can then be used by search so I can correlate search results to terms in my term store?

If someone at Microsoft can be confused by this, it's very likely many other people are as well. The article in a reply from Chris O'Brien covers it. but does it make sense to a normal person?

Explain PowerApps Licensing Scheme for Citizen Developers

Article Suggestion

New licensing options for PowerApps go into effect on 1 Oct 2019. Many people are confused about how this will affect them as citizen developers or makers. An article which explains the impacts to them (and stays valid over time) would be very useful.

Thanks for your contribution! Sharing is caring.

What is retention and how does it work in practical terms?

Retention is a thorny concept. Not only do many organizations think they either need to retain everything or nothing, but the mechanics of how it works in Office 365 is complicated.

For example, if you are migrating content into Office 365 from an external source (on premises SharePoint, or any other source), you almost always WON'T want to have ANY retention policies in place as you go through that effort, or else you will end up with MANY copies of documents in the Preservation Hold Libraries which you neither want, nor need.

Retention policies shouldn't be put in place until a site/library/whatever is "ready" (whatever that means in your context).

Why SharePoint Training is important

Article suggestion

Describe / give evidence as to why SharePoint Admins / Users training is important.

Submission Guidelines

From my experience, SharePoint is really misunderstood. Organisations (very) often neglect or underestimate the need for users training, throw users in the 'wild' and hope for the best, or simply don't use the platform because "too complex".

I'd like to talk about:

  • Mainly SharePoint as a platform, but briefly mention the integration with other apps
  • Why it's beneficial for users (and/or admins) to have some SharePoint training (daily tasks & efficiency)
  • This is not a waste of time nor money

Repo update and thanks

@nyoung30 @pkbullock @veronicageek @pealmasa @PatD @tom-daly @juliemturner @SusanHanley @joannecklein @hugoabernier @eemancini

As the premier set of contributors to this repo, @VesaJuvonen and I truly thank you! (He didn't say to include him, but I know how he feels.) We're about to launch the docs.microsoft.com version of the repo, and we couldn't have gotten to this point without you! The docs folks have been impressed with our progress, and I believe we can continue to impress them.

Of course, impressing the docs folks isn't the goal. We want to add value for the community in a way Microsoft has not tried in the past - at least in this form. We'd like to see if we can get some more activity flowing, so here are some steps we'd like to take.

Clean up assigned issues

@nyoung30 @ScottShearer @PatD @pkbullock

Each of you has at least one open issue assigned to you - generally because you asked to be assigned. Could you each please check the issues you have assigned to you and add a comment saying:

  1. You'll commit to writing something in the next few weeks
  2. You think the issue is no longer important - and why
  3. Indicate that you'd like us to assign someone else

Once we get your feedback, we'll start promoting the unassigned issues to get more community traction.

Review the articles you've written for freshness and validity

Nothing stays constant in this world, and there may have been changes since you wrote your articles. If you could take a pass through them to see if you still consider them valid, that would be great. We will undoubtedly set up a more rigorous review cycle in the future, but we'd like to be sure we have content with veracity for the launch.

Generate new article suggestions

Have other ideas you'd like to add? Totally cool, even if you can't take them on yourself.

Thanks again for all your work and help!!! Stay tuned!

Flow Introduction

An article explaining the basics of Flow as it relates to SharePoint would be helpful.
The article should include an explanation of what Flow is designed to do as well as a comparison to SharePoint Designer workflows.
If this suggstion is accepted, I would be willing to create/contribute the article.

Managing SharePoint security, a team perspective

Article suggestion

How to setup SharePoint security groups, ad groups, site permissions, feature permissions, lock downs, aspects for each type of team may use, any pros/cons and best practices.

"What is" paragraphs on each feature

Article suggestion

This is something that crops up a lot in documentation, a brief description say no more than 1-2 paragraphs on What is SharePoint, What are Content Types, What is....X

I have built a collection of mini summaries, that i put in documentation to explain in the simplest terms what that feature is, its quite often i explain to different clients what X feature does in solutions.

Update power platform licensing for citizen developer article to include new RPA License!

Article issue

https://github.com/MicrosoftDocs/microsoft-365-community/blob/live/Community/powerplatformlicensingforcitizendeveloper.md needs to add the new bits in the licensing guide! https://flow.microsoft.com/pricing specifically and https://go.microsoft.com/fwlink/?linkid=2085130 in general

assign it to bigpix2000 the author who is ready to fix it albeit it will be a few days to confirm all the bits (and to try it out!) Thanks!

Clarification on 3rd paragraph: Changes to Site Columns

Certain changes to Site Columns DO in fact propagate to Lists and Libraries where they are being used.

When editing the settings of a Site Column, there is a "Update Lists" section of the form.
[screenshot?]
The "Update all list columns based on this site column?" is "Yes" by default but can be changed to "No" before saving changes; this will prevent changes to the Site Column settings from being applied to Lists/Libraries where the Site Column has been used.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

What are the typical site owner tasks and responsibilities?

What are some of the typical site owner tasks, responsibilities and best practices? Some items to consider:

  • User support. At what point does the site owner escalate to IT?
  • Security membership review, approval, renewal etc.
  • Site closure and expiration review and action.
  • Item recovery including version history and Recycle Bin.
  • Monitor site capacity.
  • Create new site assets (libraries, unique security groups etc).

How do those tasks get accomplished and at what recommended frequency?

Information Architecture - List and Library "Limits"

People are often confused by the supposed 5000 item "limit". I have complained about it many times. In reality, it isn't a "limit". There are ways to mitigate the issues with "large" lists:

  • There’s no need to divide by 5000. It’s all about the use cases.
  • The more realistic “limit” now is 20k items, but even that is a list view threshold. It’s always been a “list view threshold”, not a “limit”.
  • When you build a list you expect to get larger than 20k items (especially on initial load), you should index the columns you expect to sort or filter by manually if you know. Remember that a view needs to be filtered first by a column which reduces the number of items below 5000, then any other column(s).
  • The column limit is about how many lookup columns there are (and Person or Group columns are lookup columns). You can’t have more than 12 per view.
  • You can have millions of items/docs in lists; it all depends what you want to do with them.

Let's frame all of this in a scenario illustrating what someone might encounter and how to think about solving their issues.

Tie ins: Power Apps. Power Automate

Related Content

Information Architecture - Content Types

Article suggestion

Content Types are a critical part of an effective information architecture in SharePoint. Can you describe how they work and how to go about building out a useful set?

CDS - Related fields

Related field logical names should be suffixed with id so a many - to - one relationship from an entity called measure to an entity called session would be pub_sessionid.

Relationship table names should be renamed to pub_measure_N1_session.

Example architectures e.g Intranet and DMS

Article suggestion

From a discussion at a SharePoint Saturday, a question was asked about example implementations e.g.

  • multisite modern intranet, example architecture and suggested departments.
  • multisite document repositories.

These are more around architectural examples, what combination of features can be used to form these types of implementations.

Article for taking a solution beyond POC

Article suggestion

This article is about taking a solution beyond POC, factors to consider when putting a solution to production for Citizen Devs. Guidelines over quality, scalability, testing, security, usability.

Organizing Modern Communication Pages

In light of a recent discussion around megamenus on twitter, it struck me that there isn't clear guidance on the options for organizing page content within modern communication site(s).

E.g. Multi-Site, Multiple pages, navigation including approaches, guidance

Should I store my files in Teams or SharePoint? An understanding of behind the scene

Article suggestion

Explain what's happening behind the scene when users are creating or uploading documents/files in a Team or Channel.

Submission Guidelines

With the push in using Microsoft Teams (sometimes in a hurry due to the current circumstances), I've heard so many times organisations asking this question, and I feel there's a need to clarify, and explain what happens to files, for example:

  • Where they are (really) stored,
  • Different ways to access them depending on how you feel comfortable (Teams or SPO),
  • Are changes reflected in SPO if modifications are done in Teams,
  • Who can access/see my files

What should the IT support group look like?

Different size organizations:

  • What should the support group look like?
  • How big?
  • What skills?
  • What are the roles?

From one person shops to global enterprises, the numbers will be different, but what are the important roles?

Factors:

  • Size
  • Culture
  • Skills

Benefits of using PowerShell with SharePoint

Article suggestion
Benefits of using PowerShell with SharePoint

Talk about the different modules available for SharePoint on-prem & SPO, what's the purpose of using PowerShell, why is it so important nowadays, etc..

Checklist for helping/working a customer build out a new SharePoint site

I (as an admin/developer/builder of SharePoint) keep a non-customer/project-specific checklist of tasks to perform before handing over the keys to someone in the business.

Things like:

  • Permissions configured?
  • Customer has had training if needed?
  • Hub site yes/no?
  • Customer knows how to get support?
  • etc

I propose creating this "Site Builder/Owner: New Site Checklist" as part of the Usage Docs.

Guidance for naming columns, sites, lists

Article suggestion

This is more about best practice around naming artefacts in SharePoint, guidlines over naming, SharePoint has its quirks and good naming of lists, columns, sites etc can present a tidy and reduce technical issues later.

The article would help Citizen Devs structure things in clean ways to avoid issues later.

Explain Flow Licensing Scheme for Citizen Developers

Article Suggestion

New licensing options for Flow go into effect on 1 Oct 2019. Many people are confused about how this will affect them as citizen developers or makers. An article which explains the impacts to them (and stays valid over time) would be very useful.

Thanks for your contribution! Sharing is caring.

Azure environment issue-Could not load file or assembly ‘Newtonsoft.Json,Version=10.0.0.0’

Could not load file or assembly 'Newtonsoft.Json, Version=10.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' in Azure Functions

After copying "MicrosoftTeams" modules files into Azure Kudu environment and and tried to run the "Connect-MicrosoftTeams" and getting below error,

                   ‘Could not load file or assembly ‘Newtonsoft.Json, Version=10.0.0.0’

error

tried downgrading to Newtonsoft.Json 9.0.1. But even then the error still persist.

https://stackoverflow.com/questions/47351068/could-not-load-file-or-assembly-newtonsoft-json-version-10-0-0-0-culture-neut

Glossary Terms

Strikethrough has been added to Glossary.md, but may need a definition.

Targeted Release
Standard Release
First Release

From Twitter:

  • Team Site
  • Tenant (and Farm)
  • Governance
  • Site Collection vs Site. Root site collection vs any other site collection.
  • Licensing (Kiosk, F1, E1, etc.)
  • Taxonomy
  • List columns vs site columns vs managed metadata (term store).
  • Roll up
  • Out of the box
  • Team's team. Team site. Group. - Explaining them is clunky. Any slick way to get them across is most welcome.
  • Hub, Home, SP start page (aka SP home)

Designing for Scale

Article suggestion

Quite often, i see a fair amount of small recipes for SharePoint configuration but not configuration at scale.

So some suggestions,

  • Architecting for scale such as sites, lists, metadata, apporaches and best practices
  • Scripting for scale, ensuring consistency in your implementations

Most implementations are bigger than the unit and I don't see often any info on this.
This might be a series rather than a single article.

Error in licensing guidelines

Article issue

Article Title: Understanding Power Platform Licensing
Link: https://docs.microsoft.com/en-us/microsoft-365/community/powerplatformlicensingforcitizendeveloper

In the Licensing by Platform section, under "Run Unlimited Apps" – Per User/Per Month (e.g. US$ 40), there is a copy/paste error. The bullet point:

  • Sometimes referred to as the "Per App" Plan

is incorrect and should be deleted. This was probably copied from the "Run Single Apps" section and wasn't deleted.

Review of guidelines for site usage

https://docs.microsoft.com/en-us/sharepoint/sites-usage-guidelines

Category

  • Question
  • Typo
  • Bug
  • Additional article idea

Review of guidelines for site usage

Recently, a new article was added in the SharePoint Online Get Started section for admins. It's title is Create guidelines for sites usage. The stated goal is to provide a template for customized guidance for site owners on how sites are set up and managed.

I'd propose it would be valuable for sp-usage-docs members to review the article and submit issues or pull requests that could improve it. It seems like improving guidance like that article is inline with the goals of this community. I believe the perspective of the community practicing in the field is very valuable for this type of scenario based help.

CDS and Model-Driven Apps Naming Conventions

Article suggestion

After a quick survey of the Power Community on Twitter, there don't seem to be any written standards for naming and other conventions around CDS and model-driven apps. Having some sort of guidelines for the community would be useful to ensure higher quality solutions.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.