When you use sealed bidding, only users who are set as the contact person for a vendor can view, edit, and submit bids for that vendor until the bidding period expires. Step 1: Set up user access to sealed bidding This section describes the prerequisites that must be in place before you can send out RFQs that require sealed bidding. The system accesses the key vault on demand, whenever encryption and decryption are required. This encryption is kept safe in a key vault that is owned by the organization that runs Dynamics 365 Supply Chain Management. The system integrates with Microsoft Azure Key Vault to generate and manage the encryption keys that are used to encrypt sealed bids. Sealed bidding uses asymmetric encryption to encrypt the bid encryption key (KEK) and symmetric encryption to encrypt the actual bid. You are solely responsible for complying with all applicable laws or regulations concerning sealed bidding. Microsoft does not provide technical or other support for any modifications, extensions, new forms, or business logic made by you or any third party on your behalf.

Microsoft is not responsible for any damages arising from any modifications or extensions to forms, or any new forms or business logic that you create, or any third party creates for you. You bear the risk of using any modifications, extensions, new forms or business logic, or the inability to use the sealed bidding feature due to such modifications, extensions, new forms, or business logic. Modifying or extending forms, or creating new forms or business logic may defeat the protection Microsoft provides for sealed bidding.

Failure to get the bid key jbidwatcher