Microsoft Dynamics 365 & Power Platform Community blog articles provide comprehensive support and how-to help for users and highlight the expertise of community members. Blog articles are an effective way to help answer questions, give tips, and provide advice.

If you want to create a new community blog (hosted blog): You can request a new blog to be created in the Microsoft Dynamics 365 & Power Platform Community. Please read the content guidelines below and skip to fill out the request form below (you must be a community member and be logged in).

Please note - we are currently not accepting new blog requests for the following Dynamics 365 on-premises products: CRM | AX | NAV | GP | SL

If you already have an external blog: You can request that your external blog be syndicated to a community blog page. The blog must meet the content guidelines listed below. You must also include a link on your external blog pointing to the Microsoft Dynamics 365 & Power Platform Community: 

If you want to update an existing hosted blog title or description: You can submit a request to the Microsoft Dynamics 365 & Power Platform Community team to specify the change needed and include the blog URL in Community. 

Content guidelines

1. Content must be written for end users, IT professionals, or developers of a Microsoft Dynamics 365 & Power Platform Community products.
2. Ideally content should be specific to a particular Microsoft Dynamics 365 & Power Platform Community product, for inclusion in that product community. Content may be either non-technical or technical content. The blog is not to be used for marketing one’s business or services or promoting competing products.
3. Licensing, branding, and pricing information is not allowed, and could result in your post and/or blog being disabled.
4. The tone of the content must be professional, business-oriented and focused on Microsoft Dynamics 365 & Power Platform Community product-related topics, as opposed to issues of personal or non-business nature.
5. Blog content should be presented in English and use good sentence structure with good spelling.
6. Content must follow the Microsoft Dynamics 365 & Power Platform Community or Microsoft Code of Conduct or Microsoft Terms of Use.
7. The author must confirm that all content published is not plagiarized or syndicated from another source. If using AI/ChatGPT to provide answers to forum questions, each answer must be checked for accuracy, and to confirm that it answers the question asked.

Request form

• Power Platform Community Support Form: aka.ms/PPCommSupport

• Dynamics 365 Community Support Form: aka.ms/D365CommunitySupport

• Blog Name -- Be as descriptive as possible, avoiding general titles such as Microsoft Dynamics 365 News & Highlights.
• Description -- Give readers a brief idea of the topic and direction of articles in less than 250 characters- this text will appear on the blog page.
• Dynamics 365 & Power Platform Application -- Select an area of focus within the Dynamics 365 & Power Platform Application in which you would like your blog to belong. Viewers will still be able to find your blog from other groups via standard search or tag search.
• RSS 2.0 feed URL - For syndicated blogs, we need the RSS 2.0 feed URL for the external blog, which may (but not necessarily) look something like this: www.blog.com/d365/feed/ 
• Writing Samples -- For hosted blogs, we ask that you include at least 3 writing samples that demonstrate your ability to write about Microsoft Dynamics technology-related subject; or, if you have an external blog, provide the URL so we can take a look.
   

Hosted blog author tips

1. When logged in and on any blog landing page, you should see a 'Create blog post' button on the right side, above the search field.
2. When the create-post form appears, the first 'Blog' dropdown menu will display blogs for which you have edit access
3. The 'Synopsis' field allows authors to define which text appears on a post on the parent blog landing page; if none is specified, the first few lines of the blog post will be shown.
4. The 'published date' field is for defining the date that you want the blog post to be automatically published.
5. Comments are disabled by default, but can be enabled via the 'Allow commenting on this blog post' checkbox
6. If the post will be a 'featured' post in the blog, you can upload a thumbnail image. Note that this image will only appear on the main blog landing page, and only if it is designated as a featured post; all other posts will appear under the featured posts (max of 4 featured posts). To mark a post as featured, send a request to the community managers and provide the blog URL and post title.
7. Select Upload or select image from the library: Upload a suitable thumbnail image for your blog post; see guidelines below.
8. 
   
   
   Image Upload Guidelines:
9. Supported Formats: JPG, JPEG, PNG
   Maximum File Size: 5MB (smaller images load faster)
   Minimum Width: 250 pixels (No height restriction)
   Optimal Dimensions: 1024x565 pixels for the best fit
   Thumbnail Preview: Your blog’s thumbnail will only be shown if the blog is featured.
   To get your blog featured, please reach out to the Community Managers.
   Images not meeting the minimum width may appear stretched or pixelated.
10. Select either Save and preview or Save and submit to finish.
11. Selecting Save and preview will save the blog as a draft and it will not appear on the blog landing page. The draft is accessible with the direct link for review. You may also view your blog drafts from your My activity page.
12. Selecting Save and submit will make you blog active, and once the publish date you selected has arrived the blog post will be visible on the blog landing page.
13. Only the specific author listed as the post author can edit an existing published post
14. To insert an image in the post body, use the editor insert tool, not cut/paste.
15. To unpublish a blog article:
    1. Go to the blog article (logged in as the author) and select the 'Edit' link near top-right of article
    2. Select 'Next' on page 1
    3. Select 'Save and preview' to remove the article from public view and put it into draft status.