-
Notifications
You must be signed in to change notification settings - Fork 132
Create index.md #2223
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Create index.md #2223
Conversation
This blog highlights why group‑based access is essential for effective SharePoint Online governance within Microsoft 365. It explains how direct user permissions lead to permission sprawl, audit challenges, and security risks, while group‑based models provide structure, accountability, and lifecycle management. By adopting groups as the default access method, organizations can reduce risk, simplify audits, enforce least‑privilege principles, and scale collaboration securely. The article offers practical steps for auditing existing permissions, replacing direct assignments with groups, and maturing governance practices to achieve safer, more resilient SharePoint environments.
|
thanks for contributing! would you also like to include an image that can serve as a thumbnail? Please reference it in the yaml at the top of your md file. |
|
Hi Luise,
Happy New Year!
Could you guide me on this occasion? I am still learning on how to do this
properly. I have attached it here.
Kind regards,
Josiah
…On Thu, Jan 1, 2026 at 10:40 AM Luise Freese ***@***.***> wrote:
*LuiseFreese* left a comment (pnp/blog#2223)
<#2223 (comment)>
thanks for contributing! would you also like to include an image that can
serve as a thumbnail? Please reference it in the yaml at the top of your md
file.
—
Reply to this email directly, view it on GitHub
<#2223 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5D6DYFPKHC7KQMCWQA7UHD4ET2QPAVCNFSM6AAAAACPOSWQKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMBTGUZDQNBVGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Sure. Inside of the folder with your index.md, create another folder called images:
- images/thumbnail.pngcommit again :-) |
Updated thumbnail image
|
Thanks Luise,
I have updated it as guided.
…On Thu, Jan 1, 2026 at 12:55 PM Luise Freese ***@***.***> wrote:
*LuiseFreese* left a comment (pnp/blog#2223)
<#2223 (comment)>
Sure. Inside of the folder with your index.md, create another folder
called images. Put your image in there, name it for example thumbnail.png.
In the YAML at the top of your md file, insert a new line
images:
- images/thumbnail.png
commit again :-)
—
Reply to this email directly, view it on GitHub
<#2223 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5D6DYA7CEWQBXXTHBOTZED4EUKKTAVCNFSM6AAAAACPOSWQKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMBTGY3DIMJWGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Hi again, it’s really important that you stick to the correct indentation in the YAML, otherwise it will break the build. You can see examples in all other blog posts in the content/posts folder. |
|
Hi Luise,
I’m currently encountering some difficulty with this and would appreciate
your guidance. Could you please help me understand what might be incorrect
on my end—whether it relates to the image dimensions or another aspect?
As this is my first time working on this, I’m keen to ensure I’m
approaching it correctly and learning best practices as I go. Any direction
or pointers you can share would be very helpful.
Thank you for your patience and support.
…On Thu, Jan 1, 2026 at 1:56 PM Luise Freese ***@***.***> wrote:
*LuiseFreese* left a comment (pnp/blog#2223)
<#2223 (comment)>
Hi again, it’s really important that you stick to the correct indentation
in the YAML, otherwise it will break the build. You can see examples in all
other blog posts in the content/posts folder.
—
Reply to this email directly, view it on GitHub
<#2223 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5D6DYGW3S2FMAOCRYJPQE34EURRHAVCNFSM6AAAAACPOSWQKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMBTG4ZDCMRTGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|

This blog post highlights why group‑based access is essential for effective SharePoint Online governance within Microsoft 365. It explains how direct user permissions lead to permission sprawl, audit challenges, and security risks, while group‑based models provide structure, accountability, and lifecycle management. By adopting groups as the default access method, organizations can reduce risk, simplify audits, enforce least‑privilege principles, and scale collaboration securely. The article offers practical steps for auditing existing permissions, replacing direct assignments with groups, and maturing governance practices to achieve safer, more resilient SharePoint environments.
Category
Contents of the Pull Request
This blog post highlights why group‑based access is essential for effective SharePoint Online governance within Microsoft 365. It explains how direct user permissions lead to permission sprawl, audit challenges, and security risks, while group‑based models provide structure, accountability, and lifecycle management. By adopting groups as the default access method, organizations can reduce risk, simplify audits, enforce least‑privilege principles, and scale collaboration securely. The article offers practical steps for auditing existing permissions, replacing direct assignments with groups, and maturing governance practices to achieve safer, more resilient SharePoint environments.