├── .github ├── ISSUE_TEMPLATE │ ├── catalog-change-request.yml │ ├── config.yml │ ├── content-request.yml │ ├── error-report.yml │ ├── new-business-process-area-draft.yml │ ├── new-business-process-draft.yml │ └── new-pattern-draft.yml └── workflows │ └── auto-assign.yml ├── .gitignore ├── CODEOWNERS ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md ├── LICENSE ├── LICENSE-ASSETS ├── README.md ├── SECURITY.md ├── SUPPORT.md ├── architectures ├── readme.md ├── reference-architecture-dynamics-365-travel-hospitality.pptx ├── saga-pattern-with-dataverse-or-dynamics-365.ppt ├── scheduled-data-exports-from-dynamics-ce-to-csv-diagram.vsdx └── scheduled-data-exports-from-dynamics-ce-to-csv-referencearchitecture.jpg ├── business-process-catalog ├── BPC - Acquire to Dispose May 2025.xlsx ├── BPC - Administer to Operate May 2025.xlsx ├── BPC - Case to Resolution May 2025.xlsx ├── BPC - Concept to Market May 2025.xlsx ├── BPC - Design to Retire May 2025.xlsx ├── BPC - Forecast to Plan May 2025.xlsx ├── BPC - Hire to Retire May 2025.xlsx ├── BPC - Inventory to Deliver May 2025.xlsx ├── BPC - Order to Cash May 2025.xlsx ├── BPC - Plan to Produce May 2025.xlsx ├── BPC - Project to Profit May 2025.xlsx ├── BPC - Prospect to Quote May 2025.xlsx ├── BPC - Record to Report May 2025.xlsx ├── BPC - Service to Deliver May 2025.xlsx ├── BPC - Source to Pay May 2025.xlsx ├── Microsoft Business Process Catalog Full May 2025.xlsx ├── Microsoft Business Process Catalog Simple May 2025.xlsx └── README.md ├── graphics ├── Acquire to dispose process flow steps (AI Generated).xlsx ├── Acquire to dispose visio flow diagrams (AI Generated).vsdx ├── Case to resolution process flow data (AI Generated).xlsx ├── Case to resolution process flow diagrams (AI Generated).vsdx ├── Concept to market process flow data (AI Generated).xlsx ├── Concept to market process flow diagrams (AI Generated).vsdx ├── Design to retire process flow data (AI Generated).xlsx ├── Design to retire process flow diagrams (AI Generated).vsdx ├── Forecast to plan process flow data (AI Generated).xlsx ├── Forecast to plan process flow diagrams (AI Generated).vsdx ├── Hire to retire process flow data (AI Generated).xlsx ├── Hire to retire process flow diagrams (AI Generated).vsdx ├── Inventory to deliver process flow data (AI Generated).xlsx ├── Inventory to deliver process flow diagrams (AI Generated).vsdx ├── Order to cash process flow data (AI Generated).xlsx ├── Order to cash process flow diagrams (AI Generated).vsdx ├── Plan to produce process flow data (AI Generated).xlsx ├── Plan to produce process flow diagrams (AI Generated).vsdx ├── Project to profit process flow diagrams (AI Generated).vsdx ├── Project to profit process flow steps (AI Generated).xlsx ├── README.md ├── Record to report process flow data (AI Generated).xlsx ├── Record to report process flow diagrams (AI Generated).vsdx ├── Service to deliver process flow data (AI Generated).xlsx ├── Service to deliver process flow diagrams (AI Generated).vsdx ├── Source to pay process flow data (AI Generated).xlsx ├── Source to pay process flow diagrams (AI Generated).vsdx └── prospect-to-quote-graphics.pptx ├── sample-solutions ├── README.md └── businessprocesscatalog-mavim │ └── ImportandUpdateMicrosoftBPCinMavim_1_0_0_3.zip ├── submit-architecture └── placeholder.md ├── submit-business-processes └── placeholder.md ├── templates ├── business-processes │ ├── Business Process Guide Graphics Template.potx │ ├── L1 End-to-end business process template.dotx │ ├── L2 Business process area template.dotx │ ├── L3 Business process template.dotx │ ├── L4 Pattern - Import Data-Entity Template.dotx │ ├── L4 Pattern or Practice Template.dotx │ ├── README.md │ ├── Reference architecture template.dotx │ └── import-business-processes-ADO.md ├── implementation-projects │ └── FDD_TDD_template.docx └── reference-architectures.md └── workshops ├── Acquire to dispose workshops.docx ├── Design to retire workshops.docx ├── Forecast to plan workshops.docx ├── Hire to retire workshops.docx ├── Inventory to deliver workshops.docx ├── Order to cash workshops.docx ├── README.md └── Source to pay workshops.docx /.github/ISSUE_TEMPLATE/catalog-change-request.yml: -------------------------------------------------------------------------------- 1 | name: Business process catalog change request 2 | description: Use this issue type to register that you would like to request a change to the business process catalog. This can include adding a new row, updating an existing row, or removal of a row. 3 | title: "[CATALOG]: " 4 | labels: ["catalog", "triage"] 5 | assignees: 6 | - rachel-profitt 7 | body: 8 | - type: markdown 9 | attributes: 10 | value: | 11 | Thank you for contributing to the [Dynamics 365 business process catalog](https://learn.microsoft.com/en-us/dynamics365/guidance/business-processes/)! Registering your request here is the first step in contributing. Your request will be reviewed and approved. Not all request may be approved. Approved requests will be added to the business process catalog. Find the catalog and templates at [https://github.com/microsoft/dynamics365patternspractices/templates/business-processes](https://github.com/microsoft/dynamics365patternspractices/tree/main/templates/business-processes). If you want to contribute with architectural patterns for Dynamics 365 implementations, use the templates at [https://github.com/microsoft/dynamics365patternspractices/templates/architecture](https://github.com/microsoft/dynamics365patternspractices/tree/main/templates/architecture). We do not recommend starting work on a new article for a new business process catalog row until the catalog request is approved. You can use this request to add new business processes or new patterns and practices to the catalog. Use one issue request for each new row you want to add or update. 12 | - type: input 13 | id: contact 14 | attributes: 15 | label: Contact details 16 | description: How can we get in touch with you? 17 | placeholder: myemail@example.com 18 | validations: 19 | required: true 20 | - type: dropdown 21 | id: organization-type 22 | attributes: 23 | label: "Organization type" 24 | description: Which type of organization do you work for? 25 | options: 26 | - "Microsoft MVP" 27 | - "Partner / ISV / Independant consultant" 28 | - "Customer organization" 29 | - "Microsoft employee" 30 | validations: 31 | required: true 32 | - type: dropdown 33 | id: endtoend 34 | attributes: 35 | label: "End-to-end business process" 36 | description: Which end-to-end business process is the article related to? 37 | options: 38 | - "Acquire to dispose" 39 | - "Administer to operate" 40 | - "Case to resolution" 41 | - "Concept to market" 42 | - "Design to retire" 43 | - "Forecast to plan" 44 | - "Hire to retire" 45 | - "Inventory to deliver" 46 | - "Order to cash" 47 | - "Plan to produce" 48 | - "Procure to pay" 49 | - "Project to profit" 50 | - "Prospect to quote" 51 | - "Record to report" 52 | - "Service to cash" 53 | validations: 54 | required: true 55 | - type: input 56 | id: area-name 57 | attributes: 58 | label: "Which business process area is this article related to?" 59 | description: "Make sure you use the same name that is listed in the business process catalog." 60 | value: "Create and manage sales" 61 | validations: 62 | required: true 63 | - type: input 64 | id: process-name 65 | attributes: 66 | label: "Which business process is this article related to?" 67 | description: "Make sure you use the same name that is listed in the business process catalog." 68 | value: "Create a sales order" 69 | validations: 70 | required: true 71 | - type: input 72 | id: pattern-name 73 | attributes: 74 | label: "Which pattern or practice is this request related to?" 75 | description: "Make sure you use the same name that is listed in the business process catalog. If this is a new pattern or practice, enter the suggested name for the pattern or practice." 76 | value: "Create a sales order in the retail point of sale" 77 | validations: 78 | required: false 79 | - type: textarea 80 | id: comments 81 | attributes: 82 | label: "Please describe the suggested change. If this is an update to an existing row in the catalog, please be sure to indicate in the comments." 83 | description: "Write your comments" 84 | value: "Comments go here" 85 | validations: 86 | required: true 87 | - type: checkboxes 88 | id: terms 89 | attributes: 90 | label: Code of Conduct 91 | description: By submitting this issue, you agree to follow the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information, see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/), or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments. 92 | options: 93 | - label: I agree to follow this project's Code of Conduct 94 | required: true 95 | - type: markdown 96 | attributes: 97 | value: "## Thanks!" 98 | - type: markdown 99 | attributes: 100 | value: Thank you for contributing to the [business process guidance](https://learn.microsoft.com/en-us/dynamics365/guidance/). 101 | 102 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/config.yml: -------------------------------------------------------------------------------- 1 | blank_issues_enabled: false 2 | contact_links: 3 | - name: Submit content requests 4 | url: https://github.com/microsoft/dynamics365patternspractices/issues/new/choose 5 | about: Choose the right template for your feedback from the list above 6 | - name: Discussions 7 | url: https://github.com/microsoft/dynamics365patternspractices/discussions 8 | about: Please ask and answer questions here. 9 | - name: Email the Microsoft Dynamics 365 Guidance team 10 | url: mailto:bizprocessguide@microsoft.com 11 | about: For additional support, please email the team. 12 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/content-request.yml: -------------------------------------------------------------------------------- 1 | name: Content request 2 | description: Request a new feature or article for the Dynamics 365 guidance hub 3 | title: "[CONTENT REQUEST]: " 4 | labels: ["feature", "triage"] 5 | assignees: 6 | - edupont04 7 | body: 8 | - type: markdown 9 | attributes: 10 | value: | 11 | Thanks for submitting this content request. We triage this feedback regularly and use it to plan for future documentation improvements. Not all content requests are implemented, but we'll prioritize based on current work priorities and the tooling available. 12 | - type: input 13 | id: contact 14 | attributes: 15 | label: Contact Details 16 | description: How can we get in touch with you if we need more info? 17 | placeholder: myemail@example.com 18 | validations: 19 | required: true 20 | - type: textarea 21 | id: description 22 | attributes: 23 | label: Describe the type of article or feature on the Microsoft Learn website that you would like to see in the Dynamics 365 guidance documentation 24 | description: Also, tell us what you expected to see? 25 | placeholder: Tell us what you want to see! 26 | value: "A great new feature!" 27 | validations: 28 | required: true 29 | - type: checkboxes 30 | id: terms 31 | attributes: 32 | label: Code of Conduct 33 | description: By submitting this issue, you agree to follow the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments. 34 | options: 35 | - label: I agree to follow this project's Code of Conduct 36 | required: true -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/error-report.yml: -------------------------------------------------------------------------------- 1 | name: Error Report 2 | description: File a an error report for Dynamics 365 guidance content 3 | title: "[ERROR]: " 4 | labels: ["bug", "triage"] 5 | assignees: 6 | - rachel-profitt 7 | body: 8 | - type: markdown 9 | attributes: 10 | value: | 11 | Thanks for taking the time to submit this error report! 12 | - type: input 13 | id: contact 14 | attributes: 15 | label: Contact Details 16 | description: How can we get in touch with you if we need more info? 17 | placeholder: myemail@example.com 18 | validations: 19 | required: true 20 | - type: textarea 21 | id: description 22 | attributes: 23 | label: Describe the error you see in the documentation, or the correction you suggest 24 | description: Also, tell us what you expected to see? 25 | placeholder: Tell us what you want to see! 26 | value: "Something is wrong in the content!" 27 | validations: 28 | required: true 29 | - type: input 30 | id: siteURL 31 | attributes: 32 | label: Link to the article where the error is 33 | description: Please copy and paste the link to the article or place on Microsoft Learn where the error or correction is needed. 34 | validations: 35 | required: true 36 | - type: checkboxes 37 | id: terms 38 | attributes: 39 | label: Code of Conduct 40 | description: By submitting this issue, you agree to follow the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments. 41 | options: 42 | - label: I agree to follow this project's Code of Conduct 43 | required: true -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/new-business-process-area-draft.yml: -------------------------------------------------------------------------------- 1 | name: New business process area 2 | description: Use this issue type to indicate that you are beginning work on a new business process area article. The business process area should already be listed in the business process catalog. 3 | title: "[AREA]: " 4 | labels: ["area", "triage"] 5 | assignees: 6 | - rachel-profitt 7 | body: 8 | - type: markdown 9 | attributes: 10 | value: | 11 | Thanks for taking the to contribute to the [Dynamics 365 business process guidance](https://learn.microsoft.com/en-us/dynamics365/guidance/business-processes/). Registering your work here is the first step in contributing. Learn more [here](https://learn.microsoft.com/en-us/dynamics365/get-started/contribute#register-your-work). 12 | - type: input 13 | id: contact 14 | attributes: 15 | label: Contact details 16 | description: How can we get in touch with you? 17 | placeholder: myemail@example.com 18 | validations: 19 | required: true 20 | - type: dropdown 21 | id: organization-type 22 | attributes: 23 | label: "Organization type" 24 | description: Which type of organization do you work for? 25 | options: 26 | - "Partner / ISV / Independant consultant" 27 | - "Customer organization" 28 | - "Microsoft MVP" 29 | - "Microsoft employee" 30 | validations: 31 | required: true 32 | - type: dropdown 33 | id: endtoend 34 | attributes: 35 | label: "End-to-end business process" 36 | description: Which end-to-end business process is the article related to? 37 | options: 38 | - "Acquire to dispose" 39 | - "Administer to operate" 40 | - "Case to resolution" 41 | - "Concept to market" 42 | - "Design to retire" 43 | - "Forecast to plan" 44 | - "Hire to retire" 45 | - "Inventory to deliver" 46 | - "Order to cash" 47 | - "Plan to produce" 48 | - "Procure to pay" 49 | - "Project to profit" 50 | - "Prospect to quote" 51 | - "Record to report" 52 | - "Service to cash" 53 | validations: 54 | required: true 55 | - type: input 56 | id: area-name 57 | attributes: 58 | label: "Which business process area is this article related to?" 59 | description: "Make sure to use the same name that is listed in the business process catalog." 60 | value: "Create and manage sales" 61 | validations: 62 | required: true 63 | - type: textarea 64 | id: comments 65 | attributes: 66 | label: "Enter any additional comments or information you want us to know." 67 | description: "Write the comments" 68 | value: "Comments go here" 69 | validations: 70 | required: false 71 | - type: input 72 | id: expected-date 73 | attributes: 74 | label: "Specify the date you expect the article to be completed and ready for review." 75 | description: "Please include the month, date, and year in the format mm/dd/yyyy" 76 | value: "01/24/2024" 77 | validations: 78 | required: true 79 | - type: checkboxes 80 | id: terms 81 | attributes: 82 | label: Code of Conduct 83 | description: By submitting this issue, you agree to follow the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments. 84 | options: 85 | - label: I agree to follow this project's Code of Conduct 86 | required: true 87 | - type: markdown 88 | attributes: 89 | value: "## Thanks!" 90 | - type: markdown 91 | attributes: 92 | value: Thank you for contributing to the [business process guidance](https://learn.microsoft.com/en-us/dynamics365/guidance/business-processes/). 93 | 94 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/new-business-process-draft.yml: -------------------------------------------------------------------------------- 1 | name: New business process 2 | description: Use this issue type to indicate that you are beginning work on a new business process article. The business process should already exist in the business process catalog. 3 | title: "[BUSINESS PROCESS]: " 4 | labels: ["business process", "triage"] 5 | assignees: 6 | - rachel-profitt 7 | body: 8 | - type: markdown 9 | attributes: 10 | value: | 11 | Thanks for contributing to the business process guidance! Registering your work here is the first step in contributing. Learn more [here](https://learn.microsoft.com/en-us/dynamics365/get-started/contribute#register-your-work). 12 | - type: input 13 | id: contact 14 | attributes: 15 | label: Contact details 16 | description: How can we get in touch with you? 17 | placeholder: myemail@example.com 18 | validations: 19 | required: true 20 | - type: dropdown 21 | id: organization-type 22 | attributes: 23 | label: "Organization type" 24 | description: Which type of organization do you work for? 25 | options: 26 | - "Parnter / ISV / Independant consultant" 27 | - "Customer organization" 28 | - "Microsoft MVP" 29 | - "Microsoft employee" 30 | validations: 31 | required: true 32 | - type: dropdown 33 | id: endtoend 34 | attributes: 35 | label: "End-to-end business process" 36 | description: Which end-to-end business process is the article related to? 37 | options: 38 | - "Acquire to dispose" 39 | - "Administer to operate" 40 | - "Case to resolution" 41 | - "Concept to market" 42 | - "Design to retire" 43 | - "Forecast to plan" 44 | - "Hire to retire" 45 | - "Inventory to deliver" 46 | - "Order to cash" 47 | - "Plan to produce" 48 | - "Procure to pay" 49 | - "Project to profit" 50 | - "Prospect to quote" 51 | - "Record to report" 52 | - "Service to cash" 53 | validations: 54 | required: true 55 | - type: input 56 | id: area-name 57 | attributes: 58 | label: "Which business process area is this article related to?" 59 | description: "Make sure you use the same name that is listed in the business process catalog." 60 | value: "Create and manage sales" 61 | validations: 62 | required: true 63 | - type: input 64 | id: process-name 65 | attributes: 66 | label: "Enter the name of the business process you are starting work on" 67 | description: "Make sure you use the same name that is listed in the business process catalog." 68 | value: "Create a sales order" 69 | validations: 70 | required: true 71 | - type: textarea 72 | id: comments 73 | attributes: 74 | label: "Enter any additional comments or information you want us to know." 75 | description: "Write the comments" 76 | value: "Comments go here" 77 | validations: 78 | required: false 79 | - type: input 80 | id: expected-date 81 | attributes: 82 | label: "Specify the date you expect the article to be completed and ready for review." 83 | description: "Please include the month, date, and year in the format mm/dd/yyyy" 84 | value: "01/24/2024" 85 | validations: 86 | required: true 87 | - type: checkboxes 88 | id: terms 89 | attributes: 90 | label: Code of Conduct 91 | description: By submitting this issue, you agree to follow the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments. 92 | options: 93 | - label: I agree to follow this project's Code of Conduct 94 | required: true 95 | - type: markdown 96 | attributes: 97 | value: "## Thanks!" 98 | - type: markdown 99 | attributes: 100 | value: Thank you for contributing to the [business process guidance](https://learn.microsoft.com/en-us/dynamics365/guidance/business-processes/overview)! 101 | 102 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/new-pattern-draft.yml: -------------------------------------------------------------------------------- 1 | name: New pattern or practice 2 | description: Use this issue type to register that you have started work on a new pattern or practice article for Dynamics 365 implementations. 3 | title: "[PATTERN]: " 4 | labels: ["pattern", "triage"] 5 | assignees: 6 | - rachel-profitt 7 | body: 8 | - type: markdown 9 | attributes: 10 | value: | 11 | Thank you for contributing to the [Dynamics 365 business process guidance](https://learn.microsoft.com/en-us/dynamics365/guidance/business-processes/)! Registering your work here is the first step in contributing. Your new article should already be listed in the business process catalog. Find the catalog and templates at [https://github.com/microsoft/dynamics365patternspractices/templates/business-processes](https://github.com/microsoft/dynamics365patternspractices/tree/main/templates/business-processes). If you want to contribute with architectural patterns for Dynamics 365 implementations, use the templates at [https://github.com/microsoft/dynamics365patternspractices/templates/architecture](https://github.com/microsoft/dynamics365patternspractices/tree/main/templates/architecture). 12 | - type: input 13 | id: contact 14 | attributes: 15 | label: Contact details 16 | description: How can we get in touch with you? 17 | placeholder: myemail@example.com 18 | validations: 19 | required: true 20 | - type: dropdown 21 | id: organization-type 22 | attributes: 23 | label: "Organization type" 24 | description: Which type of organization do you work for? 25 | options: 26 | - "Microsoft MVP" 27 | - "Partner / ISV / Independant consultant" 28 | - "Customer organization" 29 | - "Microsoft employee" 30 | validations: 31 | required: true 32 | - type: dropdown 33 | id: endtoend 34 | attributes: 35 | label: "End-to-end business process" 36 | description: Which end-to-end business process is the article related to? 37 | options: 38 | - "Acquire to dispose" 39 | - "Administer to operate" 40 | - "Case to resolution" 41 | - "Concept to market" 42 | - "Design to retire" 43 | - "Forecast to plan" 44 | - "Hire to retire" 45 | - "Inventory to deliver" 46 | - "Order to cash" 47 | - "Plan to produce" 48 | - "Procure to pay" 49 | - "Project to profit" 50 | - "Prospect to quote" 51 | - "Record to report" 52 | - "Service to cash" 53 | validations: 54 | required: true 55 | - type: input 56 | id: area-name 57 | attributes: 58 | label: "Which business process area is this article related to?" 59 | description: "Make sure you use the same name that is listed in the business process catalog." 60 | value: "Create and manage sales" 61 | validations: 62 | required: true 63 | - type: input 64 | id: process-name 65 | attributes: 66 | label: "Which business process is this article related to?" 67 | description: "Make sure you use the same name that is listed in the business process catalog." 68 | value: "Create a sales order" 69 | validations: 70 | required: true 71 | - type: input 72 | id: pattern-name 73 | attributes: 74 | label: "Which pattern or practice is this request related to?" 75 | description: "Enter the name of the pattern or practice you are starting work on. Make sure you use the same name that is listed in the business process catalog." 76 | value: "Create a sales order in the retail point of sale" 77 | validations: 78 | required: true 79 | - type: textarea 80 | id: comments 81 | attributes: 82 | label: "Enter any additional comments or information you want us to know." 83 | description: "Write your comments" 84 | value: "Comments go here" 85 | validations: 86 | required: false 87 | - type: input 88 | id: expected-date 89 | attributes: 90 | label: "Specify the date you expect the article to be completed and ready for review." 91 | description: "Please include the month, date, and year in the format mm/dd/yyyy" 92 | value: "01/24/2024" 93 | validations: 94 | required: true 95 | - type: checkboxes 96 | id: terms 97 | attributes: 98 | label: Code of Conduct 99 | description: By submitting this issue, you agree to follow the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information, see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/), or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments. 100 | options: 101 | - label: I agree to follow this project's Code of Conduct 102 | required: true 103 | - type: markdown 104 | attributes: 105 | value: "## Thanks!" 106 | - type: markdown 107 | attributes: 108 | value: Thank you for contributing to the [business process guidance](https://learn.microsoft.com/en-us/dynamics365/guidance/). 109 | 110 | -------------------------------------------------------------------------------- /.github/workflows/auto-assign.yml: -------------------------------------------------------------------------------- 1 | name: Automatic Issue Assignment 2 | on: 3 | issues: 4 | types: [opened] 5 | jobs: 6 | assign: 7 | runs-on: ubuntu-latest 8 | steps: 9 | - name: Assign issue based on business process 10 | uses: actions/github-script@v5 11 | with: 12 | script: | 13 | const issueBody = context.payload.issue.body; 14 | const processMap = { 15 | //'Acquire to dispose': 'Harshad', 16 | //'Administer to operate': 'Harsh', 17 | //'Case to resolution': 'Vinoth', 18 | //'Concept to market': 'Jinal', 19 | //'Design to retire': 'Alejandra', 20 | 'Forecast to plan': 'riblack-microsoft', 21 | //'Hire to retire': 'Priyanka', 22 | //'Inventory to deliver': 'Nicole', 23 | //'Order to cash': 'Nikhil', 24 | //'Plan to produce': 'Phillip', 25 | 'Procure to pay': 'AdiVijayashankar', 26 | //'Project to profit': 'Lalitha', 27 | //'Prospect to quote': 'Kody', 28 | 'Record to report': 'kgiardini', 29 | 'Service to cash': 'Dean-Hardy' 30 | }; 31 | const match = /End-to-End Business Process.*\n.*\[(.*)\]/i.exec(issueBody); 32 | const selectedProcess = match ? match[1].trim() : null; 33 | const assignee = processMap[selectedProcess]; 34 | if (assignee) { 35 | github.issues.addAssignees({ 36 | owner: context.repo.owner, 37 | repo: context.repo.repo, 38 | issue_number: context.payload.issue.number, 39 | assignees: [assignee] 40 | }); 41 | } 42 | 43 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | ## Ignore Visual Studio temporary files, build results, and 2 | ## files generated by popular Visual Studio add-ons. 3 | ## 4 | ## Get latest from https://github.com/github/gitignore/blob/master/VisualStudio.gitignore 5 | 6 | # User-specific files 7 | *.rsuser 8 | *.suo 9 | *.user 10 | *.userosscache 11 | *.sln.docstates 12 | 13 | # User-specific files (MonoDevelop/Xamarin Studio) 14 | *.userprefs 15 | 16 | # Mono auto generated files 17 | mono_crash.* 18 | 19 | # Build results 20 | [Dd]ebug/ 21 | [Dd]ebugPublic/ 22 | [Rr]elease/ 23 | [Rr]eleases/ 24 | x64/ 25 | x86/ 26 | [Aa][Rr][Mm]/ 27 | [Aa][Rr][Mm]64/ 28 | bld/ 29 | [Bb]in/ 30 | [Oo]bj/ 31 | [Ll]og/ 32 | [Ll]ogs/ 33 | 34 | # Visual Studio 2015/2017 cache/options directory 35 | .vs/ 36 | # Uncomment if you have tasks that create the project's static files in wwwroot 37 | #wwwroot/ 38 | 39 | # Visual Studio 2017 auto generated files 40 | Generated\ Files/ 41 | 42 | # MSTest test Results 43 | [Tt]est[Rr]esult*/ 44 | [Bb]uild[Ll]og.* 45 | 46 | # NUnit 47 | *.VisualState.xml 48 | TestResult.xml 49 | nunit-*.xml 50 | 51 | # Build Results of an ATL Project 52 | [Dd]ebugPS/ 53 | [Rr]eleasePS/ 54 | dlldata.c 55 | 56 | # Benchmark Results 57 | BenchmarkDotNet.Artifacts/ 58 | 59 | # .NET Core 60 | project.lock.json 61 | project.fragment.lock.json 62 | artifacts/ 63 | 64 | # StyleCop 65 | StyleCopReport.xml 66 | 67 | # Files built by Visual Studio 68 | *_i.c 69 | *_p.c 70 | *_h.h 71 | *.ilk 72 | *.meta 73 | *.obj 74 | *.iobj 75 | *.pch 76 | *.pdb 77 | *.ipdb 78 | *.pgc 79 | *.pgd 80 | *.rsp 81 | *.sbr 82 | *.tlb 83 | *.tli 84 | *.tlh 85 | *.tmp 86 | *.tmp_proj 87 | *_wpftmp.csproj 88 | *.log 89 | *.vspscc 90 | *.vssscc 91 | .builds 92 | *.pidb 93 | *.svclog 94 | *.scc 95 | 96 | # Chutzpah Test files 97 | _Chutzpah* 98 | 99 | # Visual C++ cache files 100 | ipch/ 101 | *.aps 102 | *.ncb 103 | *.opendb 104 | *.opensdf 105 | *.sdf 106 | *.cachefile 107 | *.VC.db 108 | *.VC.VC.opendb 109 | 110 | # Visual Studio profiler 111 | *.psess 112 | *.vsp 113 | *.vspx 114 | *.sap 115 | 116 | # Visual Studio Trace Files 117 | *.e2e 118 | 119 | # TFS 2012 Local Workspace 120 | $tf/ 121 | 122 | # Guidance Automation Toolkit 123 | *.gpState 124 | 125 | # ReSharper is a .NET coding add-in 126 | _ReSharper*/ 127 | *.[Rr]e[Ss]harper 128 | *.DotSettings.user 129 | 130 | # TeamCity is a build add-in 131 | _TeamCity* 132 | 133 | # DotCover is a Code Coverage Tool 134 | *.dotCover 135 | 136 | # AxoCover is a Code Coverage Tool 137 | .axoCover/* 138 | !.axoCover/settings.json 139 | 140 | # Visual Studio code coverage results 141 | *.coverage 142 | *.coveragexml 143 | 144 | # NCrunch 145 | _NCrunch_* 146 | .*crunch*.local.xml 147 | nCrunchTemp_* 148 | 149 | # MightyMoose 150 | *.mm.* 151 | AutoTest.Net/ 152 | 153 | # Web workbench (sass) 154 | .sass-cache/ 155 | 156 | # Installshield output folder 157 | [Ee]xpress/ 158 | 159 | # DocProject is a documentation generator add-in 160 | DocProject/buildhelp/ 161 | DocProject/Help/*.HxT 162 | DocProject/Help/*.HxC 163 | DocProject/Help/*.hhc 164 | DocProject/Help/*.hhk 165 | DocProject/Help/*.hhp 166 | DocProject/Help/Html2 167 | DocProject/Help/html 168 | 169 | # Click-Once directory 170 | publish/ 171 | 172 | # Publish Web Output 173 | *.[Pp]ublish.xml 174 | *.azurePubxml 175 | # Note: Comment the next line if you want to checkin your web deploy settings, 176 | # but database connection strings (with potential passwords) will be unencrypted 177 | *.pubxml 178 | *.publishproj 179 | 180 | # Microsoft Azure Web App publish settings. Comment the next line if you want to 181 | # checkin your Azure Web App publish settings, but sensitive information contained 182 | # in these scripts will be unencrypted 183 | PublishScripts/ 184 | 185 | # NuGet Packages 186 | *.nupkg 187 | # NuGet Symbol Packages 188 | *.snupkg 189 | # The packages folder can be ignored because of Package Restore 190 | **/[Pp]ackages/* 191 | # except build/, which is used as an MSBuild target. 192 | !**/[Pp]ackages/build/ 193 | # Uncomment if necessary however generally it will be regenerated when needed 194 | #!**/[Pp]ackages/repositories.config 195 | # NuGet v3's project.json files produces more ignorable files 196 | *.nuget.props 197 | *.nuget.targets 198 | 199 | # Microsoft Azure Build Output 200 | csx/ 201 | *.build.csdef 202 | 203 | # Microsoft Azure Emulator 204 | ecf/ 205 | rcf/ 206 | 207 | # Windows Store app package directories and files 208 | AppPackages/ 209 | BundleArtifacts/ 210 | Package.StoreAssociation.xml 211 | _pkginfo.txt 212 | *.appx 213 | *.appxbundle 214 | *.appxupload 215 | 216 | # Visual Studio cache files 217 | # files ending in .cache can be ignored 218 | *.[Cc]ache 219 | # but keep track of directories ending in .cache 220 | !?*.[Cc]ache/ 221 | 222 | # Others 223 | ClientBin/ 224 | ~$* 225 | *~ 226 | *.dbmdl 227 | *.dbproj.schemaview 228 | *.jfm 229 | *.pfx 230 | *.publishsettings 231 | orleans.codegen.cs 232 | 233 | # Including strong name files can present a security risk 234 | # (https://github.com/github/gitignore/pull/2483#issue-259490424) 235 | #*.snk 236 | 237 | # Since there are multiple workflows, uncomment next line to ignore bower_components 238 | # (https://github.com/github/gitignore/pull/1529#issuecomment-104372622) 239 | #bower_components/ 240 | 241 | # RIA/Silverlight projects 242 | Generated_Code/ 243 | 244 | # Backup & report files from converting an old project file 245 | # to a newer Visual Studio version. Backup files are not needed, 246 | # because we have git ;-) 247 | _UpgradeReport_Files/ 248 | Backup*/ 249 | UpgradeLog*.XML 250 | UpgradeLog*.htm 251 | ServiceFabricBackup/ 252 | *.rptproj.bak 253 | 254 | # SQL Server files 255 | *.mdf 256 | *.ldf 257 | *.ndf 258 | 259 | # Business Intelligence projects 260 | *.rdl.data 261 | *.bim.layout 262 | *.bim_*.settings 263 | *.rptproj.rsuser 264 | *- [Bb]ackup.rdl 265 | *- [Bb]ackup ([0-9]).rdl 266 | *- [Bb]ackup ([0-9][0-9]).rdl 267 | 268 | # Microsoft Fakes 269 | FakesAssemblies/ 270 | 271 | # GhostDoc plugin setting file 272 | *.GhostDoc.xml 273 | 274 | # Node.js Tools for Visual Studio 275 | .ntvs_analysis.dat 276 | node_modules/ 277 | 278 | # Visual Studio 6 build log 279 | *.plg 280 | 281 | # Visual Studio 6 workspace options file 282 | *.opt 283 | 284 | # Visual Studio 6 auto-generated workspace file (contains which files were open etc.) 285 | *.vbw 286 | 287 | # Visual Studio LightSwitch build output 288 | **/*.HTMLClient/GeneratedArtifacts 289 | **/*.DesktopClient/GeneratedArtifacts 290 | **/*.DesktopClient/ModelManifest.xml 291 | **/*.Server/GeneratedArtifacts 292 | **/*.Server/ModelManifest.xml 293 | _Pvt_Extensions 294 | 295 | # Paket dependency manager 296 | .paket/paket.exe 297 | paket-files/ 298 | 299 | # FAKE - F# Make 300 | .fake/ 301 | 302 | # CodeRush personal settings 303 | .cr/personal 304 | 305 | # Python Tools for Visual Studio (PTVS) 306 | __pycache__/ 307 | *.pyc 308 | 309 | # Cake - Uncomment if you are using it 310 | # tools/** 311 | # !tools/packages.config 312 | 313 | # Tabs Studio 314 | *.tss 315 | 316 | # Telerik's JustMock configuration file 317 | *.jmconfig 318 | 319 | # BizTalk build output 320 | *.btp.cs 321 | *.btm.cs 322 | *.odx.cs 323 | *.xsd.cs 324 | 325 | # OpenCover UI analysis results 326 | OpenCover/ 327 | 328 | # Azure Stream Analytics local run output 329 | ASALocalRun/ 330 | 331 | # MSBuild Binary and Structured Log 332 | *.binlog 333 | 334 | # NVidia Nsight GPU debugger configuration file 335 | *.nvuser 336 | 337 | # MFractors (Xamarin productivity tool) working folder 338 | .mfractor/ 339 | 340 | # Local History for Visual Studio 341 | .localhistory/ 342 | 343 | # BeatPulse healthcheck temp database 344 | healthchecksdb 345 | 346 | # Backup folder for Package Reference Convert tool in Visual Studio 2017 347 | MigrationBackup/ 348 | 349 | # Ionide (cross platform F# VS Code tools) working folder 350 | .ionide/ 351 | -------------------------------------------------------------------------------- /CODEOWNERS: -------------------------------------------------------------------------------- 1 | /templates/business-processes/ @rachel-profitt 2 | /templates/architecture/ @edupont04 -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Microsoft Open Source Code of Conduct 2 | 3 | This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). 4 | 5 | Resources: 6 | 7 | - [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/) 8 | - [Microsoft Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) 9 | - Contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with questions or concerns 10 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing 2 | 3 | This project welcomes contributions and suggestions. Most contributions require you to agree to a 4 | Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us 5 | the rights to use your contribution. For details, visit [https://cla.opensource.microsoft.com](https://cla.opensource.microsoft.com). 6 | 7 | When you submit a pull request, a CLA bot will automatically determine whether you need to provide 8 | a CLA and decorate the PR appropriately (such as a status check or comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA. 9 | 10 | - If you want to contribute with business process content, use the templates at [https://github.com/microsoft/dynamics365patternspractices/tree/main/templates/business-processes](https://github.com/microsoft/dynamics365patternspractices/tree/main/templates/business-processes) 11 | 12 | Submit your contribution at [https://aka.ms/D365SubmitPnP](https://aka.ms/D365SubmitPnP) 13 | 14 | - If you want to contribute with architectural guidance, use the templates at [https://github.com/microsoft/dynamics365patternspractices/tree/main/templates/architecture](https://github.com/microsoft/dynamics365patternspractices/tree/main/templates/architecture) 15 | 16 | Submit your contribution as a pull request here in this repo. Learn more about getting started in the [Get started](#get-started) section 17 | 18 | - If you want to contribute with purely conceptual content, use the templates at [https://github.com/MicrosoftDocs/dynamics365-docs-templates](https://github.com/MicrosoftDocs/dynamics365-docs-templates) 19 | 20 | Learn more at [https://learn.microsoft.com/dynamics365/get-started/contribute](https://learn.microsoft.com/dynamics365/get-started/contribute). 21 | 22 | ## Get started 23 | 24 | 1. Fork this repo 25 | 26 | To submit guidance content for Dynamics 365, you cannot work directly in the repo, so the first thing you need to do is create a fork of the repo under your GitHub account. A fork basically is copy of this repo that lets you work freely on the content without affecting the original *dynamics365patternspractices* repo. For more information, see [Fork a Repo](https://help.github.com/articles/fork-a-repo/). 27 | 28 | 2. Install GitHub Desktop (optional) and clone your forked repo. 29 | 30 | GitHub Desktop makes is easy to work and collaborate with repos locally from your own desktop. For more information, see [GitHub Desktop](https://desktop.github.com/). 31 | 32 | 3. Choose the relevant template, and copy it to a relevant location on your device. 33 | 34 | Optionally, use Visual Studio Code and the Microsoft Learn Authoring Pack to author your Markdown files. If you want to submit Word documents with business process content, follow the guidance at [https://learn.microsoft.com/dynamics365/get-started/contribute](https://learn.microsoft.com/dynamics365/get-started/contribute). 35 | 36 | ## Trademarks 37 | 38 | This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow [Microsoft's Trademark & Brand Guidelines](https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/general). 39 | Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. 40 | Any use of third-party trademarks or logos are subject to those third-party's policies. 41 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Attribution 4.0 International 2 | 3 | ======================================================================= 4 | 5 | Creative Commons Corporation ("Creative Commons") is not a law firm and 6 | does not provide legal services or legal advice. Distribution of 7 | Creative Commons public licenses does not create a lawyer-client or 8 | other relationship. Creative Commons makes its licenses and related 9 | information available on an "as-is" basis. Creative Commons gives no 10 | warranties regarding its licenses, any material licensed under their 11 | terms and conditions, or any related information. Creative Commons 12 | disclaims all liability for damages resulting from their use to the 13 | fullest extent possible. 14 | 15 | Using Creative Commons Public Licenses 16 | 17 | Creative Commons public licenses provide a standard set of terms and 18 | conditions that creators and other rights holders may use to share 19 | original works of authorship and other material subject to copyright 20 | and certain other rights specified in the public license below. The 21 | following considerations are for informational purposes only, are not 22 | exhaustive, and do not form part of our licenses. 23 | 24 | Considerations for licensors: Our public licenses are 25 | intended for use by those authorized to give the public 26 | permission to use material in ways otherwise restricted by 27 | copyright and certain other rights. Our licenses are 28 | irrevocable. Licensors should read and understand the terms 29 | and conditions of the license they choose before applying it. 30 | Licensors should also secure all rights necessary before 31 | applying our licenses so that the public can reuse the 32 | material as expected. Licensors should clearly mark any 33 | material not subject to the license. This includes other CC- 34 | licensed material, or material used under an exception or 35 | limitation to copyright. More considerations for licensors: 36 | wiki.creativecommons.org/Considerations_for_licensors 37 | 38 | Considerations for the public: By using one of our public 39 | licenses, a licensor grants the public permission to use the 40 | licensed material under specified terms and conditions. If 41 | the licensor's permission is not necessary for any reason--for 42 | example, because of any applicable exception or limitation to 43 | copyright--then that use is not regulated by the license. Our 44 | licenses grant only permissions under copyright and certain 45 | other rights that a licensor has authority to grant. Use of 46 | the licensed material may still be restricted for other 47 | reasons, including because others have copyright or other 48 | rights in the material. A licensor may make special requests, 49 | such as asking that all changes be marked or described. 50 | Although not required by our licenses, you are encouraged to 51 | respect those requests where reasonable. More_considerations 52 | for the public: 53 | wiki.creativecommons.org/Considerations_for_licensees 54 | 55 | ======================================================================= 56 | 57 | Creative Commons Attribution 4.0 International Public License 58 | 59 | By exercising the Licensed Rights (defined below), You accept and agree 60 | to be bound by the terms and conditions of this Creative Commons 61 | Attribution 4.0 International Public License ("Public License"). To the 62 | extent this Public License may be interpreted as a contract, You are 63 | granted the Licensed Rights in consideration of Your acceptance of 64 | these terms and conditions, and the Licensor grants You such rights in 65 | consideration of benefits the Licensor receives from making the 66 | Licensed Material available under these terms and conditions. 67 | 68 | 69 | Section 1 -- Definitions. 70 | 71 | a. Adapted Material means material subject to Copyright and Similar 72 | Rights that is derived from or based upon the Licensed Material 73 | and in which the Licensed Material is translated, altered, 74 | arranged, transformed, or otherwise modified in a manner requiring 75 | permission under the Copyright and Similar Rights held by the 76 | Licensor. For purposes of this Public License, where the Licensed 77 | Material is a musical work, performance, or sound recording, 78 | Adapted Material is always produced where the Licensed Material is 79 | synched in timed relation with a moving image. 80 | 81 | b. Adapter's License means the license You apply to Your Copyright 82 | and Similar Rights in Your contributions to Adapted Material in 83 | accordance with the terms and conditions of this Public License. 84 | 85 | c. Copyright and Similar Rights means copyright and/or similar rights 86 | closely related to copyright including, without limitation, 87 | performance, broadcast, sound recording, and Sui Generis Database 88 | Rights, without regard to how the rights are labeled or 89 | categorized. For purposes of this Public License, the rights 90 | specified in Section 2(b)(1)-(2) are not Copyright and Similar 91 | Rights. 92 | 93 | d. Effective Technological Measures means those measures that, in the 94 | absence of proper authority, may not be circumvented under laws 95 | fulfilling obligations under Article 11 of the WIPO Copyright 96 | Treaty adopted on December 20, 1996, and/or similar international 97 | agreements. 98 | 99 | e. Exceptions and Limitations means fair use, fair dealing, and/or 100 | any other exception or limitation to Copyright and Similar Rights 101 | that applies to Your use of the Licensed Material. 102 | 103 | f. Licensed Material means the artistic or literary work, database, 104 | or other material to which the Licensor applied this Public 105 | License. 106 | 107 | g. Licensed Rights means the rights granted to You subject to the 108 | terms and conditions of this Public License, which are limited to 109 | all Copyright and Similar Rights that apply to Your use of the 110 | Licensed Material and that the Licensor has authority to license. 111 | 112 | h. Licensor means the individual(s) or entity(ies) granting rights 113 | under this Public License. 114 | 115 | i. Share means to provide material to the public by any means or 116 | process that requires permission under the Licensed Rights, such 117 | as reproduction, public display, public performance, distribution, 118 | dissemination, communication, or importation, and to make material 119 | available to the public including in ways that members of the 120 | public may access the material from a place and at a time 121 | individually chosen by them. 122 | 123 | j. Sui Generis Database Rights means rights other than copyright 124 | resulting from Directive 96/9/EC of the European Parliament and of 125 | the Council of 11 March 1996 on the legal protection of databases, 126 | as amended and/or succeeded, as well as other essentially 127 | equivalent rights anywhere in the world. 128 | 129 | k. You means the individual or entity exercising the Licensed Rights 130 | under this Public License. Your has a corresponding meaning. 131 | 132 | 133 | Section 2 -- Scope. 134 | 135 | a. License grant. 136 | 137 | 1. Subject to the terms and conditions of this Public License, 138 | the Licensor hereby grants You a worldwide, royalty-free, 139 | non-sublicensable, non-exclusive, irrevocable license to 140 | exercise the Licensed Rights in the Licensed Material to: 141 | 142 | a. reproduce and Share the Licensed Material, in whole or 143 | in part; and 144 | 145 | b. produce, reproduce, and Share Adapted Material. 146 | 147 | 2. Exceptions and Limitations. For the avoidance of doubt, where 148 | Exceptions and Limitations apply to Your use, this Public 149 | License does not apply, and You do not need to comply with 150 | its terms and conditions. 151 | 152 | 3. Term. The term of this Public License is specified in Section 153 | 6(a). 154 | 155 | 4. Media and formats; technical modifications allowed. The 156 | Licensor authorizes You to exercise the Licensed Rights in 157 | all media and formats whether now known or hereafter created, 158 | and to make technical modifications necessary to do so. The 159 | Licensor waives and/or agrees not to assert any right or 160 | authority to forbid You from making technical modifications 161 | necessary to exercise the Licensed Rights, including 162 | technical modifications necessary to circumvent Effective 163 | Technological Measures. For purposes of this Public License, 164 | simply making modifications authorized by this Section 2(a) 165 | (4) never produces Adapted Material. 166 | 167 | 5. Downstream recipients. 168 | 169 | a. Offer from the Licensor -- Licensed Material. Every 170 | recipient of the Licensed Material automatically 171 | receives an offer from the Licensor to exercise the 172 | Licensed Rights under the terms and conditions of this 173 | Public License. 174 | 175 | b. No downstream restrictions. You may not offer or impose 176 | any additional or different terms or conditions on, or 177 | apply any Effective Technological Measures to, the 178 | Licensed Material if doing so restricts exercise of the 179 | Licensed Rights by any recipient of the Licensed 180 | Material. 181 | 182 | 6. No endorsement. Nothing in this Public License constitutes or 183 | may be construed as permission to assert or imply that You 184 | are, or that Your use of the Licensed Material is, connected 185 | with, or sponsored, endorsed, or granted official status by, 186 | the Licensor or others designated to receive attribution as 187 | provided in Section 3(a)(1)(A)(i). 188 | 189 | b. Other rights. 190 | 191 | 1. Moral rights, such as the right of integrity, are not 192 | licensed under this Public License, nor are publicity, 193 | privacy, and/or other similar personality rights; however, to 194 | the extent possible, the Licensor waives and/or agrees not to 195 | assert any such rights held by the Licensor to the limited 196 | extent necessary to allow You to exercise the Licensed 197 | Rights, but not otherwise. 198 | 199 | 2. Patent and trademark rights are not licensed under this 200 | Public License. 201 | 202 | 3. To the extent possible, the Licensor waives any right to 203 | collect royalties from You for the exercise of the Licensed 204 | Rights, whether directly or through a collecting society 205 | under any voluntary or waivable statutory or compulsory 206 | licensing scheme. In all other cases the Licensor expressly 207 | reserves any right to collect such royalties. 208 | 209 | 210 | Section 3 -- License Conditions. 211 | 212 | Your exercise of the Licensed Rights is expressly made subject to the 213 | following conditions. 214 | 215 | a. Attribution. 216 | 217 | 1. If You Share the Licensed Material (including in modified 218 | form), You must: 219 | 220 | a. retain the following if it is supplied by the Licensor 221 | with the Licensed Material: 222 | 223 | i. identification of the creator(s) of the Licensed 224 | Material and any others designated to receive 225 | attribution, in any reasonable manner requested by 226 | the Licensor (including by pseudonym if 227 | designated); 228 | 229 | ii. a copyright notice; 230 | 231 | iii. a notice that refers to this Public License; 232 | 233 | iv. a notice that refers to the disclaimer of 234 | warranties; 235 | 236 | v. a URI or hyperlink to the Licensed Material to the 237 | extent reasonably practicable; 238 | 239 | b. indicate if You modified the Licensed Material and 240 | retain an indication of any previous modifications; and 241 | 242 | c. indicate the Licensed Material is licensed under this 243 | Public License, and include the text of, or the URI or 244 | hyperlink to, this Public License. 245 | 246 | 2. You may satisfy the conditions in Section 3(a)(1) in any 247 | reasonable manner based on the medium, means, and context in 248 | which You Share the Licensed Material. For example, it may be 249 | reasonable to satisfy the conditions by providing a URI or 250 | hyperlink to a resource that includes the required 251 | information. 252 | 253 | 3. If requested by the Licensor, You must remove any of the 254 | information required by Section 3(a)(1)(A) to the extent 255 | reasonably practicable. 256 | 257 | 4. If You Share Adapted Material You produce, the Adapter's 258 | License You apply must not prevent recipients of the Adapted 259 | Material from complying with this Public License. 260 | 261 | 262 | Section 4 -- Sui Generis Database Rights. 263 | 264 | Where the Licensed Rights include Sui Generis Database Rights that 265 | apply to Your use of the Licensed Material: 266 | 267 | a. for the avoidance of doubt, Section 2(a)(1) grants You the right 268 | to extract, reuse, reproduce, and Share all or a substantial 269 | portion of the contents of the database; 270 | 271 | b. if You include all or a substantial portion of the database 272 | contents in a database in which You have Sui Generis Database 273 | Rights, then the database in which You have Sui Generis Database 274 | Rights (but not its individual contents) is Adapted Material; and 275 | 276 | c. You must comply with the conditions in Section 3(a) if You Share 277 | all or a substantial portion of the contents of the database. 278 | 279 | For the avoidance of doubt, this Section 4 supplements and does not 280 | replace Your obligations under this Public License where the Licensed 281 | Rights include other Copyright and Similar Rights. 282 | 283 | 284 | Section 5 -- Disclaimer of Warranties and Limitation of Liability. 285 | 286 | a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE 287 | EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS 288 | AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF 289 | ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, 290 | IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, 291 | WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR 292 | PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, 293 | ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT 294 | KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT 295 | ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. 296 | 297 | b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE 298 | TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, 299 | NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, 300 | INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, 301 | COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR 302 | USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN 303 | ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR 304 | DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR 305 | IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. 306 | 307 | c. The disclaimer of warranties and limitation of liability provided 308 | above shall be interpreted in a manner that, to the extent 309 | possible, most closely approximates an absolute disclaimer and 310 | waiver of all liability. 311 | 312 | 313 | Section 6 -- Term and Termination. 314 | 315 | a. This Public License applies for the term of the Copyright and 316 | Similar Rights licensed here. However, if You fail to comply with 317 | this Public License, then Your rights under this Public License 318 | terminate automatically. 319 | 320 | b. Where Your right to use the Licensed Material has terminated under 321 | Section 6(a), it reinstates: 322 | 323 | 1. automatically as of the date the violation is cured, provided 324 | it is cured within 30 days of Your discovery of the 325 | violation; or 326 | 327 | 2. upon express reinstatement by the Licensor. 328 | 329 | For the avoidance of doubt, this Section 6(b) does not affect any 330 | right the Licensor may have to seek remedies for Your violations 331 | of this Public License. 332 | 333 | c. For the avoidance of doubt, the Licensor may also offer the 334 | Licensed Material under separate terms or conditions or stop 335 | distributing the Licensed Material at any time; however, doing so 336 | will not terminate this Public License. 337 | 338 | d. Sections 1, 5, 6, 7, and 8 survive termination of this Public 339 | License. 340 | 341 | 342 | Section 7 -- Other Terms and Conditions. 343 | 344 | a. The Licensor shall not be bound by any additional or different 345 | terms or conditions communicated by You unless expressly agreed. 346 | 347 | b. Any arrangements, understandings, or agreements regarding the 348 | Licensed Material not stated herein are separate from and 349 | independent of the terms and conditions of this Public License. 350 | 351 | 352 | Section 8 -- Interpretation. 353 | 354 | a. For the avoidance of doubt, this Public License does not, and 355 | shall not be interpreted to, reduce, limit, restrict, or impose 356 | conditions on any use of the Licensed Material that could lawfully 357 | be made without permission under this Public License. 358 | 359 | b. To the extent possible, if any provision of this Public License is 360 | deemed unenforceable, it shall be automatically reformed to the 361 | minimum extent necessary to make it enforceable. If the provision 362 | cannot be reformed, it shall be severed from this Public License 363 | without affecting the enforceability of the remaining terms and 364 | conditions. 365 | 366 | c. No term or condition of this Public License will be waived and no 367 | failure to comply consented to unless expressly agreed to by the 368 | Licensor. 369 | 370 | d. Nothing in this Public License constitutes or may be interpreted 371 | as a limitation upon, or waiver of, any privileges and immunities 372 | that apply to the Licensor or You, including from the legal 373 | processes of any jurisdiction or authority. 374 | 375 | 376 | ======================================================================= 377 | 378 | Creative Commons is not a party to its public 379 | licenses. Notwithstanding, Creative Commons may elect to apply one of 380 | its public licenses to material it publishes and in those instances 381 | will be considered the “Licensor.” The text of the Creative Commons 382 | public licenses is dedicated to the public domain under the CC0 Public 383 | Domain Dedication. Except for the limited purpose of indicating that 384 | material is shared under a Creative Commons public license or as 385 | otherwise permitted by the Creative Commons policies published at 386 | creativecommons.org/policies, Creative Commons does not authorize the 387 | use of the trademark "Creative Commons" or any other trademark or logo 388 | of Creative Commons without its prior written consent including, 389 | without limitation, in connection with any unauthorized modifications 390 | to any of its public licenses or any other arrangements, 391 | understandings, or agreements concerning use of licensed material. For 392 | the avoidance of doubt, this paragraph does not form part of the 393 | public licenses. 394 | 395 | Creative Commons may be contacted at creativecommons.org. 396 | -------------------------------------------------------------------------------- /LICENSE-ASSETS: -------------------------------------------------------------------------------- 1 | Creative Commons Attribution-ShareAlike 4.0 International Public License 2 | 3 | By exercising the Licensed Rights (defined below), You accept and agree to be bound by the terms and conditions of this Creative Commons Attribution-ShareAlike 4.0 International Public License ("Public License"). To the extent this Public License may be interpreted as a contract, You are granted the Licensed Rights in consideration of Your acceptance of these terms and conditions, and the Licensor grants You such rights in consideration of benefits the Licensor receives from making the Licensed Material available under these terms and conditions. 4 | 5 | Section 1 – Definitions. 6 | 7 | a. Adapted Material means material subject to Copyright and Similar Rights that is derived from or based upon the Licensed Material and in which the Licensed Material is translated, altered, arranged, transformed, or otherwise modified in a manner requiring permission under the Copyright and Similar Rights held by the Licensor. For purposes of this Public License, where the Licensed Material is a musical work, performance, or sound recording, Adapted Material is always produced where the Licensed Material is synched in timed relation with a moving image. 8 | b. Adapter's License means the license You apply to Your Copyright and Similar Rights in Your contributions to Adapted Material in accordance with the terms and conditions of this Public License. 9 | c. BY-SA Compatible License means a license listed at creativecommons.org/compatiblelicenses, approved by Creative Commons as essentially the equivalent of this Public License. 10 | d. Copyright and Similar Rights means copyright and/or similar rights closely related to copyright including, without limitation, performance, broadcast, sound recording, and Sui Generis Database Rights, without regard to how the rights are labeled or categorized. For purposes of this Public License, the rights specified in Section 2(b)(1)-(2) are not Copyright and Similar Rights. 11 | e. Effective Technological Measures means those measures that, in the absence of proper authority, may not be circumvented under laws fulfilling obligations under Article 11 of the WIPO Copyright Treaty adopted on December 20, 1996, and/or similar international agreements. 12 | f. Exceptions and Limitations means fair use, fair dealing, and/or any other exception or limitation to Copyright and Similar Rights that applies to Your use of the Licensed Material. 13 | g. License Elements means the license attributes listed in the name of a Creative Commons Public License. The License Elements of this Public License are Attribution and ShareAlike. 14 | h. Licensed Material means the artistic or literary work, database, or other material to which the Licensor applied this Public License. 15 | i. Licensed Rights means the rights granted to You subject to the terms and conditions of this Public License, which are limited to all Copyright and Similar Rights that apply to Your use of the Licensed Material and that the Licensor has authority to license. 16 | j. Licensor means the individual(s) or entity(ies) granting rights under this Public License. 17 | k. Share means to provide material to the public by any means or process that requires permission under the Licensed Rights, such as reproduction, public display, public performance, distribution, dissemination, communication, or importation, and to make material available to the public including in ways that members of the public may access the material from a place and at a time individually chosen by them. 18 | l. Sui Generis Database Rights means rights other than copyright resulting from Directive 96/9/EC of the European Parliament and of the Council of 11 March 1996 on the legal protection of databases, as amended and/or succeeded, as well as other essentially equivalent rights anywhere in the world. 19 | m. You means the individual or entity exercising the Licensed Rights under this Public License. Your has a corresponding meaning. 20 | 21 | Section 2 – Scope. 22 | 23 | a. License grant. 24 | 1. Subject to the terms and conditions of this Public License, the Licensor hereby grants You a worldwide, royalty-free, non-sublicensable, non-exclusive, irrevocable license to exercise the Licensed Rights in the Licensed Material to: 25 | A. reproduce and Share the Licensed Material, in whole or in part; and 26 | B. produce, reproduce, and Share Adapted Material. 27 | 2. Exceptions and Limitations. For the avoidance of doubt, where Exceptions and Limitations apply to Your use, this Public License does not apply, and You do not need to comply with its terms and conditions. 28 | 3. Term. The term of this Public License is specified in Section 6(a). 29 | 4. Media and formats; technical modifications allowed. The Licensor authorizes You to exercise the Licensed Rights in all media and formats whether now known or hereafter created, and to make technical modifications necessary to do so. The Licensor waives and/or agrees not to assert any right or authority to forbid You from making technical modifications necessary to exercise the Licensed Rights, including technical modifications necessary to circumvent Effective Technological Measures. For purposes of this Public License, simply making modifications authorized by this Section 2(a)(4) never produces Adapted Material. 30 | 5. Downstream recipients. 31 | A. Offer from the Licensor – Licensed Material. Every recipient of the Licensed Material automatically receives an offer from the Licensor to exercise the Licensed Rights under the terms and conditions of this Public License. 32 | B. Additional offer from the Licensor – Adapted Material. Every recipient of Adapted Material from You automatically receives an offer from the Licensor to exercise the Licensed Rights in the Adapted Material under the conditions of the Adapter’s License You apply. 33 | C. No downstream restrictions. You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, the Licensed Material if doing so restricts exercise of the Licensed Rights by any recipient of the Licensed Material. 34 | 6. No endorsement. Nothing in this Public License constitutes or may be construed as permission to assert or imply that You are, or that Your use of the Licensed Material is, connected with, or sponsored, endorsed, or granted official status by, the Licensor or others designated to receive attribution as provided in Section 3(a)(1)(A)(i). 35 | 36 | b. Other rights. 37 | 38 | 1. Moral rights, such as the right of integrity, are not licensed under this Public License, nor are publicity, privacy, and/or other similar personality rights; however, to the extent possible, the Licensor waives and/or agrees not to assert any such rights held by the Licensor to the limited extent necessary to allow You to exercise the Licensed Rights, but not otherwise. 39 | 2. Patent and trademark rights are not licensed under this Public License. 40 | 3. To the extent possible, the Licensor waives any right to collect royalties from You for the exercise of the Licensed Rights, whether directly or through a collecting society under any voluntary or waivable statutory or compulsory licensing scheme. In all other cases the Licensor expressly reserves any right to collect such royalties. 41 | 42 | Section 3 – License Conditions. 43 | 44 | Your exercise of the Licensed Rights is expressly made subject to the following conditions. 45 | 46 | a. Attribution. 47 | 48 | 1. If You Share the Licensed Material (including in modified form), You must: 49 | 50 | A. retain the following if it is supplied by the Licensor with the Licensed Material: 51 | i. identification of the creator(s) of the Licensed Material and any others designated to receive attribution, in any reasonable manner requested by the Licensor (including by pseudonym if designated); 52 | ii. a copyright notice; 53 | iii. a notice that refers to this Public License; 54 | iv. a notice that refers to the disclaimer of warranties; 55 | v. a URI or hyperlink to the Licensed Material to the extent reasonably practicable; 56 | B. indicate if You modified the Licensed Material and retain an indication of any previous modifications; and 57 | C. indicate the Licensed Material is licensed under this Public License, and include the text of, or the URI or hyperlink to, this Public License. 58 | 2. You may satisfy the conditions in Section 3(a)(1) in any reasonable manner based on the medium, means, and context in which You Share the Licensed Material. For example, it may be reasonable to satisfy the conditions by providing a URI or hyperlink to a resource that includes the required information. 59 | 3. If requested by the Licensor, You must remove any of the information required by Section 3(a)(1)(A) to the extent reasonably practicable. 60 | 61 | b. ShareAlike. 62 | In addition to the conditions in Section 3(a), if You Share Adapted Material You produce, the following conditions also apply. 63 | 64 | 1. The Adapter’s License You apply must be a Creative Commons license with the same License Elements, this version or later, or a BY-SA Compatible License. 65 | 2. You must include the text of, or the URI or hyperlink to, the Adapter's License You apply. You may satisfy this condition in any reasonable manner based on the medium, means, and context in which You Share Adapted Material. 66 | 3. You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, Adapted Material that restrict exercise of the rights granted under the Adapter's License You apply. 67 | 68 | Section 4 – Sui Generis Database Rights. 69 | 70 | Where the Licensed Rights include Sui Generis Database Rights that apply to Your use of the Licensed Material: 71 | 72 | a. for the avoidance of doubt, Section 2(a)(1) grants You the right to extract, reuse, reproduce, and Share all or a substantial portion of the contents of the database; 73 | b. if You include all or a substantial portion of the database contents in a database in which You have Sui Generis Database Rights, then the database in which You have Sui Generis Database Rights (but not its individual contents) is Adapted Material, including for purposes of Section 3(b); and 74 | c. You must comply with the conditions in Section 3(a) if You Share all or a substantial portion of the contents of the database. 75 | For the avoidance of doubt, this Section 4 supplements and does not replace Your obligations under this Public License where the Licensed Rights include other Copyright and Similar Rights. 76 | 77 | Section 5 – Disclaimer of Warranties and Limitation of Liability. 78 | 79 | a. Unless otherwise separately undertaken by the Licensor, to the extent possible, the Licensor offers the Licensed Material as-is and as-available, and makes no representations or warranties of any kind concerning the Licensed Material, whether express, implied, statutory, or other. This includes, without limitation, warranties of title, merchantability, fitness for a particular purpose, non-infringement, absence of latent or other defects, accuracy, or the presence or absence of errors, whether or not known or discoverable. Where disclaimers of warranties are not allowed in full or in part, this disclaimer may not apply to You. 80 | b. To the extent possible, in no event will the Licensor be liable to You on any legal theory (including, without limitation, negligence) or otherwise for any direct, special, indirect, incidental, consequential, punitive, exemplary, or other losses, costs, expenses, or damages arising out of this Public License or use of the Licensed Material, even if the Licensor has been advised of the possibility of such losses, costs, expenses, or damages. Where a limitation of liability is not allowed in full or in part, this limitation may not apply to You. 81 | c. The disclaimer of warranties and limitation of liability provided above shall be interpreted in a manner that, to the extent possible, most closely approximates an absolute disclaimer and waiver of all liability. 82 | 83 | Section 6 – Term and Termination. 84 | 85 | a. This Public License applies for the term of the Copyright and Similar Rights licensed here. However, if You fail to comply with this Public License, then Your rights under this Public License terminate automatically. 86 | b. Where Your right to use the Licensed Material has terminated under Section 6(a), it reinstates: 87 | 88 | 1. automatically as of the date the violation is cured, provided it is cured within 30 days of Your discovery of the violation; or 89 | 2. upon express reinstatement by the Licensor. 90 | For the avoidance of doubt, this Section 6(b) does not affect any right the Licensor may have to seek remedies for Your violations of this Public License. 91 | c. For the avoidance of doubt, the Licensor may also offer the Licensed Material under separate terms or conditions or stop distributing the Licensed Material at any time; however, doing so will not terminate this Public License. 92 | d. Sections 1, 5, 6, 7, and 8 survive termination of this Public License. 93 | 94 | Section 7 – Other Terms and Conditions. 95 | 96 | a. The Licensor shall not be bound by any additional or different terms or conditions communicated by You unless expressly agreed. 97 | b. Any arrangements, understandings, or agreements regarding the Licensed Material not stated herein are separate from and independent of the terms and conditions of this Public License. 98 | 99 | Section 8 – Interpretation. 100 | 101 | a. For the avoidance of doubt, this Public License does not, and shall not be interpreted to, reduce, limit, restrict, or impose conditions on any use of the Licensed Material that could lawfully be made without permission under this Public License. 102 | b. To the extent possible, if any provision of this Public License is deemed unenforceable, it shall be automatically reformed to the minimum extent necessary to make it enforceable. If the provision cannot be reformed, it shall be severed from this Public License without affecting the enforceability of the remaining terms and conditions. 103 | c. No term or condition of this Public License will be waived and no failure to comply consented to unless expressly agreed to by the Licensor. 104 | d. Nothing in this Public License constitutes or may be interpreted as a limitation upon, or waiver of, any privileges and immunities that apply to the Licensor or You, including from the legal processes of any jurisdiction or authority. -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Dynamics 365 Patterns and Practices 2 | 3 | Welcome to the repository for patterns, practices, business process guides, and other types of guidance content for Microsoft Dynamics 365! This repo provides a way for you to actively contribute to the Dynamics 365 guidance content, and we welcome your contributions. Register your plans for a contribution as an [Issue](https://github.com/microsoft/dynamics365patternspractices/issues/new/choose), and submit the contribution as a [pull request](https://github.com/microsoft/dynamics365patternspractices/pulls). Learn more at [Contribute to Microsoft's content for Dynamics 365](https://learn.microsoft.com/en-us/dynamics365/get-started/contribute#dynamics-365-guidance-content). 4 | 5 | The *main* branch is the default branch with approved templates and other artifacts. 6 | 7 | If you have any questions, you can submit feedback as an Issue or a pull request. 8 | 9 | ## Microsoft Open Source Code of Conduct 10 | 11 | This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). 12 | For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments. 13 | 14 | ## Trademarks 15 | 16 | This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow [Microsoft's Trademark & Brand Guidelines](https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/general). 17 | Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. 18 | Any use of third-party trademarks or logos are subject to those third-party's policies. 19 | -------------------------------------------------------------------------------- /SECURITY.md: -------------------------------------------------------------------------------- 1 | # Security 2 | 3 | Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/). 4 | 5 | If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://aka.ms/opensource/security/definition), please report it to us as described below. 6 | 7 | ## Reporting Security Issues 8 | 9 | **Please do not report security vulnerabilities through public GitHub issues.** 10 | 11 | Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://aka.ms/opensource/security/create-report). 12 | 13 | If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com). If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://aka.ms/opensource/security/pgpkey). 14 | 15 | You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://aka.ms/opensource/security/msrc). 16 | 17 | Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue: 18 | 19 | * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.) 20 | * Full paths of source file(s) related to the manifestation of the issue 21 | * The location of the affected source code (tag/branch/commit or direct URL) 22 | * Any special configuration required to reproduce the issue 23 | * Step-by-step instructions to reproduce the issue 24 | * Proof-of-concept or exploit code (if possible) 25 | * Impact of the issue, including how an attacker might exploit the issue 26 | 27 | This information will help us triage your report more quickly. 28 | 29 | If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://aka.ms/opensource/security/bounty) page for more details about our active programs. 30 | 31 | ## Preferred Languages 32 | 33 | We prefer all communications to be in English. 34 | 35 | ## Policy 36 | 37 | Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://aka.ms/opensource/security/cvd). 38 | -------------------------------------------------------------------------------- /SUPPORT.md: -------------------------------------------------------------------------------- 1 | # Support 2 | 3 | ## How to file issues and get help 4 | 5 | This project uses GitHub Issues to track bugs and feature requests. Please search the existing issues before filing new issues to avoid duplicates. For new issues, file your bug or feature request as a new Issue. 6 | 7 | For help and questions about using this project, please reach out to us on Yammer, if you're external to Microsoft, or in Teams if you're internal to Microsoft. 8 | 9 | ## Microsoft Support Policy 10 | 11 | Support for this project is limited to the resources listed above. 12 | -------------------------------------------------------------------------------- /architectures/readme.md: -------------------------------------------------------------------------------- 1 | # Download reference architectures 2 | 3 | This folder contains downloadable reference architectures for solutions with Microsoft Dynamics 365 apps. Get an overview of the available architectures in the [Microsoft Dynamics 365 guidance hub](https://learn.microsoft.com/dynamics365/guidance/reference-architectures/). 4 | 5 | ## Fetch a download 6 | 7 | To download an architecture, choose the file in the explorer, and then choose the **Download raw file** icon. 8 | 9 | ## Contribute 10 | 11 | Fetch the appropriate Markdown templates from the [guidance-templates](https://github.com/MicrosoftDocs/dynamics365-docs-templates/tree/main/guidance-templates) folder in the [dynamics365-docs-templates](https://github.com/MicrosoftDocs/dynamics365-docs-templates/) GitHub repo. 12 | 13 | Learn more at [Contribute to Microsoft content for Dynamics 365](https://learn.microsoft.com/dynamics365/get-started/contribute#architectures). 14 | -------------------------------------------------------------------------------- /architectures/reference-architecture-dynamics-365-travel-hospitality.pptx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/architectures/reference-architecture-dynamics-365-travel-hospitality.pptx -------------------------------------------------------------------------------- /architectures/saga-pattern-with-dataverse-or-dynamics-365.ppt: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/architectures/saga-pattern-with-dataverse-or-dynamics-365.ppt -------------------------------------------------------------------------------- /architectures/scheduled-data-exports-from-dynamics-ce-to-csv-diagram.vsdx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/architectures/scheduled-data-exports-from-dynamics-ce-to-csv-diagram.vsdx -------------------------------------------------------------------------------- /architectures/scheduled-data-exports-from-dynamics-ce-to-csv-referencearchitecture.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/architectures/scheduled-data-exports-from-dynamics-ce-to-csv-referencearchitecture.jpg -------------------------------------------------------------------------------- /business-process-catalog/BPC - Acquire to Dispose May 2025.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/business-process-catalog/BPC - Acquire to Dispose May 2025.xlsx -------------------------------------------------------------------------------- /business-process-catalog/BPC - Administer to Operate May 2025.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/business-process-catalog/BPC - Administer to Operate May 2025.xlsx -------------------------------------------------------------------------------- /business-process-catalog/BPC - Case to Resolution May 2025.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/business-process-catalog/BPC - Case to Resolution May 2025.xlsx -------------------------------------------------------------------------------- /business-process-catalog/BPC - Concept to Market May 2025.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/business-process-catalog/BPC - Concept to Market May 2025.xlsx -------------------------------------------------------------------------------- /business-process-catalog/BPC - Design to Retire May 2025.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/business-process-catalog/BPC - Design to Retire May 2025.xlsx -------------------------------------------------------------------------------- /business-process-catalog/BPC - Forecast to Plan May 2025.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/business-process-catalog/BPC - Forecast to Plan May 2025.xlsx -------------------------------------------------------------------------------- /business-process-catalog/BPC - Hire to Retire May 2025.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/business-process-catalog/BPC - Hire to Retire May 2025.xlsx -------------------------------------------------------------------------------- /business-process-catalog/BPC - Inventory to Deliver May 2025.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/business-process-catalog/BPC - Inventory to Deliver May 2025.xlsx -------------------------------------------------------------------------------- /business-process-catalog/BPC - Order to Cash May 2025.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/business-process-catalog/BPC - Order to Cash May 2025.xlsx -------------------------------------------------------------------------------- /business-process-catalog/BPC - Plan to Produce May 2025.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/business-process-catalog/BPC - Plan to Produce May 2025.xlsx -------------------------------------------------------------------------------- /business-process-catalog/BPC - Project to Profit May 2025.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/business-process-catalog/BPC - Project to Profit May 2025.xlsx -------------------------------------------------------------------------------- /business-process-catalog/BPC - Prospect to Quote May 2025.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/business-process-catalog/BPC - Prospect to Quote May 2025.xlsx -------------------------------------------------------------------------------- /business-process-catalog/BPC - Record to Report May 2025.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/business-process-catalog/BPC - Record to Report May 2025.xlsx -------------------------------------------------------------------------------- /business-process-catalog/BPC - Service to Deliver May 2025.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/business-process-catalog/BPC - Service to Deliver May 2025.xlsx -------------------------------------------------------------------------------- /business-process-catalog/BPC - Source to Pay May 2025.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/business-process-catalog/BPC - Source to Pay May 2025.xlsx -------------------------------------------------------------------------------- /business-process-catalog/Microsoft Business Process Catalog Full May 2025.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/business-process-catalog/Microsoft Business Process Catalog Full May 2025.xlsx -------------------------------------------------------------------------------- /business-process-catalog/Microsoft Business Process Catalog Simple May 2025.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/business-process-catalog/Microsoft Business Process Catalog Simple May 2025.xlsx -------------------------------------------------------------------------------- /business-process-catalog/README.md: -------------------------------------------------------------------------------- 1 | # Microsoft Business Process Catalog 2 | The term business process covers a wide range of structured, often sequenced, activities or tasks to achieve a predetermined organizational goal. The term can also refer to the cumulative effects of all steps progressing toward a business goal. In our articles, we illustrate this sequence of steps in flowcharts. Dynamics 365 is a suite of applications that are designed to help organization meet the organizational goals aligned to a variety of business processes focused on specific industries. 3 | 4 | We've structured our business process content into four levels: 5 | 6 | - End-to-end scenarios 7 | - Areas 8 | - Business processes 9 | - Scenarios 10 | 11 | 12 | Learn more at [About business processes](https://learn.microsoft.com/en-us/dynamics365/guidance/business-processes/about). 13 | 14 | Learn more about what's new in this version of the Microsoft Business Process Catalog see [What's new or changed in the business process catalog](https://learn.microsoft.com/en-us/dynamics365/guidance/business-processes/about-whats-new). 15 | 16 | ## Supported Operating Systems 17 | 18 | Windows 11, Windows 10, Macintosh 19 | 20 | The file is a Microsoft Excel document. Users who do not have Microsoft Excel can view this document through the downloadable Excel Viewer. 21 | 22 | ## Install Instructions 23 | Choose each file you want to download and then click the Download icon in the upper right corner of the pane. 24 | 25 | Use the following link to learn more about the business process catalog and how it can be used in Dynamics 365 implementations. [Learn more](https://learn.microsoft.com/en-us/dynamics365/guidance/business-processes/about). 26 | 27 | Use the following link to learn how to import the CSV version of the catalog into Azure DevOps. [Learn more](https://learn.microsoft.com/en-us/dynamics365/guidance/business-processes/about-import-catalog-devops). 28 | -------------------------------------------------------------------------------- /graphics/Acquire to dispose process flow steps (AI Generated).xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/Acquire to dispose process flow steps (AI Generated).xlsx -------------------------------------------------------------------------------- /graphics/Acquire to dispose visio flow diagrams (AI Generated).vsdx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/Acquire to dispose visio flow diagrams (AI Generated).vsdx -------------------------------------------------------------------------------- /graphics/Case to resolution process flow data (AI Generated).xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/Case to resolution process flow data (AI Generated).xlsx -------------------------------------------------------------------------------- /graphics/Case to resolution process flow diagrams (AI Generated).vsdx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/Case to resolution process flow diagrams (AI Generated).vsdx -------------------------------------------------------------------------------- /graphics/Concept to market process flow data (AI Generated).xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/Concept to market process flow data (AI Generated).xlsx -------------------------------------------------------------------------------- /graphics/Concept to market process flow diagrams (AI Generated).vsdx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/Concept to market process flow diagrams (AI Generated).vsdx -------------------------------------------------------------------------------- /graphics/Design to retire process flow data (AI Generated).xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/Design to retire process flow data (AI Generated).xlsx -------------------------------------------------------------------------------- /graphics/Design to retire process flow diagrams (AI Generated).vsdx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/Design to retire process flow diagrams (AI Generated).vsdx -------------------------------------------------------------------------------- /graphics/Forecast to plan process flow data (AI Generated).xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/Forecast to plan process flow data (AI Generated).xlsx -------------------------------------------------------------------------------- /graphics/Forecast to plan process flow diagrams (AI Generated).vsdx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/Forecast to plan process flow diagrams (AI Generated).vsdx -------------------------------------------------------------------------------- /graphics/Hire to retire process flow data (AI Generated).xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/Hire to retire process flow data (AI Generated).xlsx -------------------------------------------------------------------------------- /graphics/Hire to retire process flow diagrams (AI Generated).vsdx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/Hire to retire process flow diagrams (AI Generated).vsdx -------------------------------------------------------------------------------- /graphics/Inventory to deliver process flow data (AI Generated).xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/Inventory to deliver process flow data (AI Generated).xlsx -------------------------------------------------------------------------------- /graphics/Inventory to deliver process flow diagrams (AI Generated).vsdx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/Inventory to deliver process flow diagrams (AI Generated).vsdx -------------------------------------------------------------------------------- /graphics/Order to cash process flow data (AI Generated).xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/Order to cash process flow data (AI Generated).xlsx -------------------------------------------------------------------------------- /graphics/Order to cash process flow diagrams (AI Generated).vsdx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/Order to cash process flow diagrams (AI Generated).vsdx -------------------------------------------------------------------------------- /graphics/Plan to produce process flow data (AI Generated).xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/Plan to produce process flow data (AI Generated).xlsx -------------------------------------------------------------------------------- /graphics/Plan to produce process flow diagrams (AI Generated).vsdx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/Plan to produce process flow diagrams (AI Generated).vsdx -------------------------------------------------------------------------------- /graphics/Project to profit process flow diagrams (AI Generated).vsdx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/Project to profit process flow diagrams (AI Generated).vsdx -------------------------------------------------------------------------------- /graphics/Project to profit process flow steps (AI Generated).xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/Project to profit process flow steps (AI Generated).xlsx -------------------------------------------------------------------------------- /graphics/README.md: -------------------------------------------------------------------------------- 1 | # Dynamics 365 Patterns and Practices graphics 2 | The graphics of each end-to-end business process, business process area, and business process are available for download in this folder. New versions of the files are published regularly as new articles are published, so we always recommend that you download the latest version each time you start a new project. The source graphics are created in a Microsoft Power Point files for accessibility and translation purposes. Each end-to-end process includes one file. The graphics inside each file are organized by using sections to sort and group the graphics by the busisness process area. We recommend that you download the graphics to help accelerate the deployment of your fit-gap anaylsis process and to understand how the process works by default with Dynamics 365 applications out of the box. Keep in mind that not all variations of business processes may be documented in a given diagram. You can easily customize the graphics for your business requirements by modifying the arrows, adding steps, or removing steps as required. 3 | -------------------------------------------------------------------------------- /graphics/Record to report process flow data (AI Generated).xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/Record to report process flow data (AI Generated).xlsx -------------------------------------------------------------------------------- /graphics/Record to report process flow diagrams (AI Generated).vsdx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/Record to report process flow diagrams (AI Generated).vsdx -------------------------------------------------------------------------------- /graphics/Service to deliver process flow data (AI Generated).xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/Service to deliver process flow data (AI Generated).xlsx -------------------------------------------------------------------------------- /graphics/Service to deliver process flow diagrams (AI Generated).vsdx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/Service to deliver process flow diagrams (AI Generated).vsdx -------------------------------------------------------------------------------- /graphics/Source to pay process flow data (AI Generated).xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/Source to pay process flow data (AI Generated).xlsx -------------------------------------------------------------------------------- /graphics/Source to pay process flow diagrams (AI Generated).vsdx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/Source to pay process flow diagrams (AI Generated).vsdx -------------------------------------------------------------------------------- /graphics/prospect-to-quote-graphics.pptx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/graphics/prospect-to-quote-graphics.pptx -------------------------------------------------------------------------------- /sample-solutions/README.md: -------------------------------------------------------------------------------- 1 | # Sample solutions for implementation projects with Dynamics 365 apps 2 | 3 | This folder contains sample solutions that you can choose to use in an implementation project. More details coming soon about how to upload sample solutions. 4 | 5 | ## Currently in this folder 6 | 7 | The folder currently contains the following sample solutions: 8 | 9 | |Name of subfolder |Description | 10 | |---------|---------| 11 | |**businessprocesscatalog-mavim** | Contains files that you can import into Power Automate so that you can import the business process catalog in Mavim. Learn more at [Import the business process catalog in Mavim using a Power Automate flow](https://learn.microsoft.com/en-us/dynamics365/guidance/business-processes/about-import-catalog-mavim). | 12 | -------------------------------------------------------------------------------- /sample-solutions/businessprocesscatalog-mavim/ImportandUpdateMicrosoftBPCinMavim_1_0_0_3.zip: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/sample-solutions/businessprocesscatalog-mavim/ImportandUpdateMicrosoftBPCinMavim_1_0_0_3.zip -------------------------------------------------------------------------------- /submit-architecture/placeholder.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Placeholder only 3 | description: Don't use this file because it doesn't do anything. 4 | author: edupont04 5 | ms.author: edupont 6 | ms.topic: article 7 | ms.reviewer: raprofit 8 | ms.date: 06/16/2023 9 | --- 10 | 11 | # Placeholder for contributions for Dynamics 365 guidance content 12 | 13 | I'm just a placeholder. You can submit a pull request with contributions to the Microsoft Dynamics 365 architecture and patterns content to this folder. Learn more at [Contribute to Microsoft's content for Dynamics 365](https://learn.microsoft.com/en-us/dynamics365/get-started/contribute#dynamics-365-guidance-content). 14 | -------------------------------------------------------------------------------- /submit-business-processes/placeholder.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Placeholder only 3 | description: Don't use this file because it doesn't do anything. 4 | author: edupont04 5 | ms.author: edupont 6 | ms.topic: article 7 | ms.reviewer: raprofit 8 | ms.date: 06/16/2023 9 | --- 10 | 11 | # Placeholder for contributions for Dynamics 365 guidance content 12 | 13 | I'm just a placeholder. You can submit a pull request with contributions to the Microsoft Dynamics 365 business process content to this folder. Learn more at [Contribute to Microsoft's content for Dynamics 365](https://learn.microsoft.com/en-us/dynamics365/get-started/contribute#dynamics-365-guidance-content). 14 | -------------------------------------------------------------------------------- /templates/business-processes/Business Process Guide Graphics Template.potx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/templates/business-processes/Business Process Guide Graphics Template.potx -------------------------------------------------------------------------------- /templates/business-processes/L1 End-to-end business process template.dotx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/templates/business-processes/L1 End-to-end business process template.dotx -------------------------------------------------------------------------------- /templates/business-processes/L2 Business process area template.dotx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/templates/business-processes/L2 Business process area template.dotx -------------------------------------------------------------------------------- /templates/business-processes/L3 Business process template.dotx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/templates/business-processes/L3 Business process template.dotx -------------------------------------------------------------------------------- /templates/business-processes/L4 Pattern - Import Data-Entity Template.dotx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/templates/business-processes/L4 Pattern - Import Data-Entity Template.dotx -------------------------------------------------------------------------------- /templates/business-processes/L4 Pattern or Practice Template.dotx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/templates/business-processes/L4 Pattern or Practice Template.dotx -------------------------------------------------------------------------------- /templates/business-processes/README.md: -------------------------------------------------------------------------------- 1 | If you have landed on this page looking for the business process catalog, you can find the catalog on the Microsoft Download Center by navigating to [https://aka.ms/businessprocesscatalog](https://aka.ms/businessprocesscatalog) 2 | -------------------------------------------------------------------------------- /templates/business-processes/Reference architecture template.dotx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/templates/business-processes/Reference architecture template.dotx -------------------------------------------------------------------------------- /templates/business-processes/import-business-processes-ADO.md: -------------------------------------------------------------------------------- 1 | --- 2 | date: 11/14/2023 3 | author: rachel-profitt 4 | --- 5 | 6 | # Import the business process catalog into Azure DevOps 7 | 8 | This article is replaced by an article in the [Dynamics 365 guidance hub](https://learn.microsoft.com/en-us/dynamics365/guidance/). Learn more at [Import the business process catalog into Azure DevOps](https://learn.microsoft.com/en-us/dynamics365/guidance/business-processes/about-import-catalog-devops). 9 | -------------------------------------------------------------------------------- /templates/implementation-projects/FDD_TDD_template.docx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/templates/implementation-projects/FDD_TDD_template.docx -------------------------------------------------------------------------------- /templates/reference-architectures.md: -------------------------------------------------------------------------------- 1 | # Reference architectures and design patterns 2 | 3 | We welcome contributions of architectural guidance, including solution ideas and design patterns. If you have a best practice or reference implementation, submit your proposal either to [the Azure team](https://learn.microsoft.com/contribute/architecture-center/aac-contribute) or to us in [Dynamics 365](https://learn.microsoft.com/dynamics365/get-started/contribute#dynamics-365-guidance-content). 4 | 5 | Fetch the appropriate Markdown templates from the [guidance-templates](https://github.com/MicrosoftDocs/dynamics365-docs-templates/tree/main/guidance-templates) folder in the [dynamics365-docs-templates](https://github.com/MicrosoftDocs/dynamics365-docs-templates/) GitHub repo. 6 | 7 | Learn more at [Contribute to Microsoft content for Dynamics 365](https://learn.microsoft.com/dynamics365/get-started/contribute#dynamics-365-guidance-content). 8 | -------------------------------------------------------------------------------- /workshops/Acquire to dispose workshops.docx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/workshops/Acquire to dispose workshops.docx -------------------------------------------------------------------------------- /workshops/Design to retire workshops.docx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/workshops/Design to retire workshops.docx -------------------------------------------------------------------------------- /workshops/Forecast to plan workshops.docx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/workshops/Forecast to plan workshops.docx -------------------------------------------------------------------------------- /workshops/Hire to retire workshops.docx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/workshops/Hire to retire workshops.docx -------------------------------------------------------------------------------- /workshops/Inventory to deliver workshops.docx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/workshops/Inventory to deliver workshops.docx -------------------------------------------------------------------------------- /workshops/Order to cash workshops.docx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/workshops/Order to cash workshops.docx -------------------------------------------------------------------------------- /workshops/README.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | # Workshops templates 4 | The business process catalog includes comprehensive set of workshop templates designed to streamline collaboration and decision-making across key business areas. These templates are structured to enhance engagement and ensure precise alignment with business goals. Below, you’ll find the core structure of the workshops, a detailed list of processes that include workshops in this release, and an overview of the three distinct workshop types: Storyboard, Storyline Design Review, and Deep-Dive Design. 5 | 6 | ## Workshop template structure 7 | Each workshop template includes: 8 | - A clear agenda to guide participants through the session’s objectives. 9 | - Pre-defined tools and resources tailored to facilitate effective collaboration. 10 | - Comprehensive instructions to ensure consistency and alignment with best practices. 11 | 12 | The templates are designed to be flexible and scalable, accommodating the unique needs of sellers, technical sellers, solution architects, and business analysts or functional consultants. 13 | 14 | ## Processes featuring workshops 15 | The following end-to-end processes include Word document tempaltes for the business process catalog 16 | - Acquire to dispose 17 | - Design to retire 18 | - Forecast to plan 19 | - Inventory to deliver 20 | - Hire to retire 21 | - Order to cash 22 | - Source to pay 23 | 24 | ## Workshop types 25 | Three workshop types are included for each end-to-end process. Each workshop template is tailored to specific stages of the business process design and refinement. 26 | - Storyboard design workshops 27 | 28 | These workshops are highly visual and focus on mapping out the entire business process. Participants collaborate to create a high-level overview of the business processes, scenarios, and objectives, identifying key milestones and potential bottlenecks. The objective is to establish a shared vision and roadmap. These workshops are recommended to be run early in the pre-sales stage of an engagement to help the team get a better understanding of the customers business needs and create a demo plan. 29 | 30 | Each storyboard design workshop includes the following components: 31 | - A storyboard graphic in the Visio file that is available for the end-to-end business process in the GitHub repository. The Visio files can be downloaded at https://aka.ms/businessprocessflow. 32 | - A Word document template for the workshop. The Word document template files can be downloaded at https://aka.ms/businessprocessworkshops. 33 | - Work items in the Azure DevOps template. This includes one Workshop type work item for the overall workshop including the details of the workshop from the template, and Tasks that are children work items under the parent Workshop work item. 34 | 35 | - Storyline design review workshops 36 | 37 | In these sessions, the primary scenario is demonstrated to the customer in Dynamics 365. Teams delve into the specifics of the business process in Dynamics 365. The goal is to review and refine the storyline behind the process and conduct a fit-to-standard analysis, ensuring all steps are aligned with strategic objectives. Feedback loops are built into the session to address gaps or inconsistencies. 38 | 39 | Each Storyline design review workshop includes the following components: 40 | - A Word document template for the workshop. The Word document template files can be downloaded at https://aka.ms/businessprocessworkshops. 41 | - Work items in the Azure DevOps template. This includes one Workshop type work item for the overall workshop including the details of the workshop from the template, and Tasks that are children work items under the parent Workshop work item. 42 | 43 | - Deep-dive design workshops 44 | 45 | These workshops are designed for thorough exploration of intricate process details. The focus is on addressing complex challenges, testing assumptions, and finalizing designs. They are particularly useful for processes requiring cross-functional alignment and technical input. These workshops are intended to be run by the implementation team in the Implement phase of a project. Each level two business process area in the catalog includes at least one Deep-dive design workshop. However, some business process areas may include multiple workshops. 46 | 47 | - A Word document template for the workshop. The Word document template files can be downloaded at https://aka.ms/businessprocessworkshops. 48 | - Work items in the Azure DevOps template. This includes one Workshop type work item for the overall workshop including the details of the workshop from the template. These workshops do not include detailed tasks. However, the catalog includes Configuration deliverables which make up much of the work functional consultants would need to do in order for the process to work according to the customers business requirements. 49 | 50 | ## Using the workshop templates in Azure DevOps 51 | 52 | While there is not one specific way to use the templates and work items provided in the business process catalog, the following list of tips and tricks can be used to help ensure good management and governance of the process: 53 | - Document each business requirement using Requirement type work items. 54 | - Document Risks, Issues, Actions, and Decisions (RAID) log items using the related work item types. 55 | - Create Task type work items to track specific tasks that need to be completed or followed up on by the project team. 56 | - Work items should be linked to the lowest possible level of the business process catalog, typically level four scenarios. However, if a business requirement is more general, it may be appropriate to link it to a higher-level business process or area. 57 | 58 | -------------------------------------------------------------------------------- /workshops/Source to pay workshops.docx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/dynamics365patternspractices/d6ddb039199c5d91249c9736622214908f864faf/workshops/Source to pay workshops.docx --------------------------------------------------------------------------------